Offline & connectivity behavior
The Zenoti Biometrics application requires a live connection to Zenoti Cloud to sign in, load center and employee data, and record attendance events. This article explains what the application can and cannot do when connectivity is unavailable, and how to recover when a connectivity error occurs.
Audience: Managers and operators who administer the Zenoti Biometrics desktop application at a center.
On this page
- Before you begin
- How connectivity affects each operation
- Steps
- Tips
- Troubleshooting
- Related articles
Before you begin
- The Zenoti Biometrics application must be installed and configured with your organization's account name and cloud URL.
- Biometric attendance must be enabled at both the organization level and the center level. For configuration details, see Installation, setup, and application lifecycle.
- Your Zenoti employee account must be authorized to use the application at the selected center. If authorization fails, the application displays an explanatory message and prevents sign-in.
- The operator's ability to sign in and use the application is determined entirely by their existing Zenoti employee account, center access, and the organization- and center-level biometric settings. The application defines no roles or permission levels of its own.
Permission: You need a Zenoti employee account with access to the selected center and the appropriate biometric attendance settings enabled at your organization and center. No separate application-level role exists.
How connectivity affects each operation
The table below summarizes which operations require a live connection to Zenoti Cloud and which do not.
| Operation | Requires connectivity | Behavior when offline |
|---|---|---|
| Sign in to the application | Yes | Sign-in fails; application remains on the sign-in screen |
| Load the list of centers | Yes | Center list cannot be retrieved |
| Load biometric-enabled employees | Yes | Employee list cannot be refreshed |
| Fingerprint identification (matching against locally stored templates) | No | Identification proceeds using locally cached templates |
| Recording a check-in or check-out event | Yes | Event cannot be recorded; application displays a connectivity error |
| Enrollment of a new fingerprint | Yes | Enrollment cannot be completed |
Important: Although the application can identify an employee from a fingerprint scan using locally stored templates, it cannot record the resulting check-in or check-out event without a live connection to Zenoti Cloud. The event is not queued for later submission β it is discarded. The employee must scan again once connectivity is restored.
Steps
Understand what happens when connectivity is lost
During sign-in β If Zenoti Cloud is unreachable when an operator attempts to sign in, authentication fails. The application displays an error message and the operator remains on the sign-in screen. No partial session is created.
During attendance mode β If connectivity is lost after the operator has signed in and attendance mode is active:
- The fingerprint scanner continues to identify employees against locally stored templates.
- When an employee places their finger on the scanner, the application identifies them but cannot record the event.
- The application displays a clear on-screen message explaining that the event could not be recorded because Zenoti Cloud is unreachable.
- The employee must scan again after connectivity is restored.
During enrollment β Fingerprint enrollment requires connectivity throughout the process. If connectivity is lost mid-enrollment, the enrollment cannot be completed and the employee must restart the process once the connection is restored.
Read the on-screen connectivity error
When the application cannot reach Zenoti Cloud, it displays a specific error message so the operator understands why the action could not be completed. The message identifies the condition β connectivity loss β rather than showing a generic failure.
- Read the error message displayed on screen. The message will indicate that Zenoti Cloud is unreachable.
- Do not attempt to retry the same action immediately. Repeated attempts while offline will produce the same result.
- Note the time the error occurred if you need to reconcile attendance records later.
Recover from a connectivity error
- Identify the cause of the connectivity loss β for example, a dropped Wi-Fi connection, a network outage, or a firewall change.
- Restore the network connection using your organization's standard IT procedures.
- Verify that the device can reach the internet and that the Zenoti Cloud URL configured in the application is accessible.
- Once connectivity is restored, attendance and enrollment actions resume automatically. You do not need to restart the application.
- Ask any employees who attempted to scan during the outage to scan again so their check-in or check-out events are recorded.
Note: The application does not queue or buffer attendance events recorded during an offline period. Any scan that occurred while Zenoti Cloud was unreachable was not recorded and must be repeated.
Tips
- Post a notice at the scanner terminal when a known network outage is in progress, so employees know to return and scan again once connectivity is restored.
- Use the audit log in the application's Logs section to review connectivity errors and confirm when the connection was restored. Navigate to Settings > Logs and select Export Audit Logs to download a record of all events including connectivity failures.
- Check the scanner status indicator on the attendance screen. A connectivity error is distinct from a scanner disconnection β confirm which condition is displayed before troubleshooting.
- Configure the application's retry settings under Settings > Application Settings > API Retry Settings to control how many times the application retries a failed cloud call and how long it waits between attempts. Increasing the retry count can help in environments with intermittent connectivity.
- Remind employees that fingerprint identification alone does not constitute a recorded check-in. The event must reach Zenoti Cloud to appear in attendance reports.
Troubleshooting
- The application shows a connectivity error but the internet appears to be working. The application connects to a specific Zenoti Cloud URL configured during setup. General internet access does not guarantee that this URL is reachable. Verify the Base URL under Settings > Cloud Configuration and confirm that the URL is accessible from the device. Check whether a firewall, proxy, or VPN change has blocked the connection.
- An employee scanned their finger but their check-in does not appear in Zenoti. If a connectivity error was displayed at the time of the scan, the event was not recorded. Ask the employee to scan again. If no error was displayed but the record is still missing, check the audit log under Settings > Logs > Export Audit Logs to confirm whether the event was attempted and whether a cloud error was returned.
- The application cannot sign in even though the network is connected. Confirm that the operator's Zenoti employee account is active and has access to the selected center. Also confirm that biometric attendance is enabled at both the organization level and the center level, and that the center's biometric scan type is set to Zenoti Biometrics. If the account or settings are correct and sign-in still fails, check whether Zenoti Cloud is experiencing a service disruption.
- Attendance mode stopped recording events mid-shift. If attendance mode was active and events stopped being recorded, a connectivity interruption likely occurred. Review the audit log for connectivity error entries around the time events stopped. Once connectivity is confirmed restored, ask affected employees to scan again. Events that occurred during the outage were not buffered and must be re-scanned.
- The application displays a "not authorized" message when selecting a center. This message appears when the signed-in operator's Zenoti employee account is not authorized to use the Zenoti Biometrics application at the selected center. Contact your Zenoti administrator to verify the operator's center access and biometric enablement settings.