Kiosk Fleet and Offline Recovery
See every kiosk tablet at a glance: is it up, how fast are clocks, are any clocks waiting to sync. Push a reload to one kiosk or all of them, and recover clocks a tablet could not send while the internet was down.
Last checked against the product:
Overview
One row per tablet.
Every kiosk reports in every 60 seconds with its state, version, match rate and the clocks it is holding. The fleet page turns that into one row per tablet with a status light, so you can spot a tablet that has gone quiet before a shift change, not after.
Before you start
- Agency console: Sites > Kiosk fleet, Admin or super admin (not in the Coordinator preset). The remote tools and the retry and clear buttons need a super admin.
- Client dashboard: Sites > Kiosk fleet, tenant manager or tenant admin. It shows that client's kiosks only, with reloads but no remote tools.
- At least one kiosk opened at a site. Kiosks appear here by themselves once they report in.
Reading the Fleet
Healthy, Warning, Down.
The cards at the top count Healthy, Warning and Down / unhealthy kiosks. Each row's Status is Green, Amber or Red.
| Status | Meaning |
|---|---|
| Green | Reported in within the last 2 minutes, normal state, match rate 95% or better. |
| Amber | Last report 2 to 5 minutes ago, or the kiosk is in PIN-only mode, or the match rate in the last hour is below 95%. |
| Red | No report for more than 5 minutes, or the match rate in the last hour is below 90%. |
| Column | What it tells you |
|---|---|
| Last seen | When the kiosk last reported in. |
| Clock time 7d | Badge entered to clock sent, measured on the tablet over 7 days: p50 is a typical worker, p90 the slow end. |
| Outbox | Clocks saved on the tablet while offline: how many are waiting, and how many failed. Failed clocks are kept on the tablet, never dropped. |
| AWS errors and Match rate | Face service errors in the last 5 minutes, and the share of face checks that matched in the last hour. |
| Version and JS exec | The kiosk app or browser version, and whether the kiosk page is up to date. An old or unknown page needs a reload. |
| Pinned location | The site the tablet is pinned to. Pinning routes its camera frames to that site. |
Use Active (24h) or All to choose which rows show. Rows for tablets not seen for 7 days or more are ghosts from reinstalls or cleared browsers: Clean up ghosts removes them, and a working kiosk comes back on its next report.
Reloading Kiosks
Push an update without visiting the site.
One kiosk
Click Reload on its row and confirm.
One client
Under Push an update:, pick the client in Reload all kiosks at… and click Reload client. Only kiosks seen in the last 24 hours are reloaded.
Everything
Click Reload all kiosks. Use this after a release.
Each kiosk picks up the reload on its next report, so a rollout takes up to a minute. The page reloads as soon as the kiosk sees it, so a worker in the middle of a clock may have to start again. Avoid reloading at a shift change.
Remote Tools
Super admin only.
Click Tools on a row to open the remote tools panel for that tablet. Commands are sent to the kiosk and run on its next check, and Recent commands shows each one as queued, delivered, done or failed.
| Section | Buttons |
|---|---|
| Connection test | Sends a ping to check the kiosk can take commands. |
| Diagnose | Capture screenshot now (reports which kiosk screen is showing; adds a camera picture only while the camera view is open), or Dump full state by email to your own account. |
| Recover | Reload kiosk page, Restart camera, Reset to entry screen, Clear local storage + reload. |
| Camera view | Watch the camera for 2 minutes and Stop the camera view. Works only at sites with the camera feed switched on; the kiosk shows a notice while it streams. |
| Offline clocks | Retry or clear failed clocks. See below. |
| Push a message | Show banner on kiosk for a set time, in Info, Warning or Error style. |
Self-test & troubleshoot at the top of the page (super admin) pings every kiosk at once and sends a test email, to show which part of the chain is broken.
Failed Offline Clocks
Nothing is thrown away. You decide what happens.
When the internet drops, a kiosk keeps face-matched clocks and sends them later. A clock the server refuses is marked failed and stays on the tablet. Common reasons: it is more than 72 hours old, the face check expired, or the kiosk was outside the site fence. Later clocks for the same worker that were waiting behind it are held, so a clock-out cannot become a false clock-in.
Find the tablet
Look for a red failed count in the Outbox column, then click Tools on that row.
Fix the cause, then retry
Click Retry failed offline clocks to send the refused clocks and the clocks they held again.
Or release the held clocks only
If the refused clock will always be refused, click Retry held clocks only. The held clocks go, the refused one stays. Add the refused clock by hand on Backfill or Manual clock.
Clear what you re-keyed
Once the clocks are added by hand, click Clear failed clocks (after re-keying) so the tablet stops reporting them.
A saved clock that clashes with a shift already on record is not a failed clock: it is listed on Time & Pay > Exceptions under Offline conflicts, where you add it as a shift or dismiss it.
If a client's face match proof is set to Enforce, face clocks made while the kiosk was offline cannot be replayed and are refused when it reconnects. Add them by hand. See Facial Recognition Explained.
Client Dashboard
The same health view for one client.
Client dashboard: Sites > Kiosk fleet. It counts Healthy, Warning and Down kiosks and lists each one with State, Last seen, Match rate (1h), Clock time (7d), Waiting to sync and Version. Click Reload on a row, or Reload all my kiosks. A tablet with failed clocks shows the count with contact support: the agency recovers them from the agency console.
Troubleshooting
Common problems.
| Problem | What to do |
|---|---|
| A kiosk is Red | Check the tablet has power and Wi-Fi. If it is on, use Reload. A silent kiosk is also emailed to agency admins: round the clock at sites marked 24/7, and Monday to Friday 09:00 to 18:00 elsewhere. |
| A kiosk is Amber in PIN-only mode | The face service could not be reached. The kiosk tries face matching again by itself after a minute. |
| A command stays queued | The kiosk page is out of date. Click Reload, wait a minute and try again. |
| The same tablet appears twice | Delete the older row with Delete, or use Clean up ghosts. |
| The Outbox shows clocks waiting for a long time | The tablet is still offline. Use the paper sign-in sheet until the connection is back. |
Know who turned up, and pay every hour right.
Face-verified clock-ins, live geofencing and payroll-ready timesheets in one system. Tell us how your shifts run and we will show you how it fits.
Hosted in the EU · Your largest site live first, with us alongside · No app needed to clock in