Attendance Logs

SyncID’s core function is collecting attendance records from devices and delivering them to SyncrOne. This guide explains the full attendance data flow.

Data flow overview

Device → SyncID (collection) → Local DB (storage) → SyncrOne (delivery)

1. Collection: Employee punches at a device → SyncID collects the record
2. Storage: Record is saved in the local SQL Server database immediately
3. Delivery: A background job sends records to SyncrOne in batches
4. Confirmation: Once SyncrOne confirms receipt, the record is marked as sent

Collection methods

Real-time event streaming

When real-time monitoring is enabled, SyncID maintains an active connection to each device and receives attendance events instantly as they occur.

Advantages:

• Near-zero latency — records arrive within seconds
• No polling overhead

Considerations:

• Requires stable network connectivity
• Uses a persistent connection per device

Polling

SyncID periodically polls each device for new records:

Advantages:

• Works with intermittent connectivity
• Less sensitive to network quality

Configuration: The polling interval is configurable in the application settings.

Network resilience

SyncID is designed for unreliable network environments:

Device-to-SyncID buffering

• If SyncID can’t reach a device, the device stores records locally
• When connectivity restores, SyncID collects all accumulated records
• This recovery happens automatically on startup

SyncID-to-SyncrOne buffering

• Records are always saved to the local database first
• Delivery to SyncrOne happens asynchronously via a background job
• If SyncrOne is unreachable, records queue locally and are retried
• SyncID automatically retries delivery with increasing delays between attempts

Zero data loss guarantee

As long as the SyncID database is intact, no attendance records are lost. Records are only removed from the local database after confirmed delivery to SyncrOne.

Viewing attendance records

Navigate to Attendance in the sidebar to see:

Column	Description
Employee	Who punched
Device	Which device recorded the punch
Timestamp	Date and time of the punch
Auth method	How they authenticated (face, fingerprint, card, PIN)
Sync status	Whether the record has been sent to SyncrOne

Filtering

Use the filters to narrow down records by:

• Date range
• Employee name or ID
• Specific device
• Sync status (Sent / Pending)

Troubleshooting

Records not appearing from a device

1. Check the device status — is it Online?
2. Verify the collection task is running from the scheduled tasks page
3. Try a manual collection from the device detail page
4. Check if the device has records stored (device info → record count)

Records stuck in “Pending” status

1. Check the health dashboard — is SyncrOne reachable?
2. Verify the attendance delivery task is not failing
3. If SyncrOne was recently down, allow a few minutes for automatic recovery
4. Review the scheduled tasks page for delivery errors

Duplicate records

SyncID deduplicates records based on employee ID, device ID, and timestamp. If you see duplicates:

• Check if the device time is drifting (enable automatic time sync)
• Verify the device serial number matches in SyncID