You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need some clarity on the scope of time being retrieved by those two options.
Live capture - is the of retrieval of the attendance records starting from the time option being enabled?
Is this the same with the scheduled option?
E.g.
Live capture or schedule capture was enabled at 8:24am. Hence only subsquent records after 8:24am are processed for capture into the system.
Which option is recommended.
Currently doing biometric live capture. However this option seems to turn off by itself overnight (don't have night shift). Is there a builtin timeout?
Live Capture : When enabled, Horilla immediately starts retrieving attendance records from the biometric device. It captures data every second using a thread. However, live capture may automatically turn off due to an inherent timeout, inactivity, server restarts, or network issues.
Scheduled Capture : Similar to live capture, scheduled capture retrieves attendance records from the biometric device but follows a user-defined schedule. For example, if set to run every minute, it will fetch data at intervals like 08:24 AM, then 08:25 AM, with up to a one-minute delay. While live capture retrieves data every second, if it turns off, any attendance records during that downtime will not be captured. However, the scheduled capture will still fetch records based on the last successful retrieval time.
Have a followup question. Since the python library retrieves all available records on the device. what would be the recommended schedule to get in/out records? End of the business day? every hour? How does horilla determine in/out? Usually, the first checkin time and last checkout time is considered here.
Horilla determines whether an attendance activity is a "clock-in" or "clock-out" based on the biometric punch code provided by the ZK device.
Specifically: Clock-In: When the punch code is one of {0, 3, 4}, Horilla interprets the action as a "clock-in." These punch codes typically represent different forms of check-ins (e.g., starting work or returning from a break).
Clock-Out: For any other punch codes not in {0, 3, 4}, Horilla interprets the activity as a "clock-out," meaning the employee is leaving or ending work.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Need some clarity on the scope of time being retrieved by those two options.
Live capture - is the of retrieval of the attendance records starting from the time option being enabled?
Is this the same with the scheduled option?
E.g.
Live capture or schedule capture was enabled at 8:24am. Hence only subsquent records after 8:24am are processed for capture into the system.
Which option is recommended.
Currently doing biometric live capture. However this option seems to turn off by itself overnight (don't have night shift). Is there a builtin timeout?
Beta Was this translation helpful? Give feedback.
All reactions