Check-in error and GPS mock reports
Use the Mobile Check-in Errors and Tablet Check-in Errors reports to find check-ins that failed: a face that did not match, a weak signal, a server timeout, a photo that did not upload. Use the GPS Mock Report to find phones that reported a fake location while checking in. These reports explain why someone looks absent when they say they checked in.
Where:
- Attendance › Tools & Reports › Mobile Check-in Errors
- Attendance › Tools & Reports › Tablet Check-in Errors
- Attendance › Tools & Reports › GPS Mock Report
You need: the My Team Reports right, on the My Team rights screen. You see only the people your access covers.
Which one, when
| The question | Use |
|---|---|
| Why did this person's check-in on their phone fail? | Mobile Check-in Errors |
| Why did the tablet by the door reject someone? | Tablet Check-in Errors |
| Is anyone faking their location? | GPS Mock Report |
| Who is struggling most, and what should I do about it? | Timekeeping Health |
| Is the tablet itself online? | Device Monitoring |
The error reports are the raw log. Timekeeping Health reads the same logs, works out the likely cause for each person and offers a fix. Start there if you are not sure what you are looking for.
How to find a failed check-in
- Go to Attendance › Tools & Reports and open Mobile Check-in Errors or Tablet Check-in Errors. Both open on today.
- Set the date range.
- Use Search Employees, or select Filters to narrow by Action, Profile or Branch. On Mobile Check-in Errors you can also type part of an error message in Errors By Reason.
- Select a row to open the error's details.
- To keep a copy, select Export, then Microsoft Excel (.xlsx).
On Mobile Check-in Errors, two panels sit above the list:
- Errors By Reason is a chart of the most common error messages.
- Errors By Employee lists the people with the most errors. Select a count to filter the list to that person.
What each error shows
The list shows Employee Name, Branch, Date, Action and Reason. Tablet Check-in Errors also shows Verification Method.
| Field | What it means |
|---|---|
| Action | What the person was doing: Check-in, Check-out, Break-in, Break-out, Take picture, Upload attachments, Face id, Start GPS or Failed identification |
| Reason | The error message the app recorded |
| Verification Method | Tablet only: Face-id, Fingerprint or NFC |
| Platform, Brand, Model | Mobile only: the phone |
| App Version | The KAMI app version on the phone or tablet |
| Roundtrip | How long the request took to come back |
| Fingerprint Quality | Tablet only: the scan's quality score, 0 to 100, when the tablet reports one |
| Event ID | The event the check-in was for, if one was found |
| Details | Extra technical detail from the app |
Some errors are KAMI's side, not the employee's: a server error or timeout, or a face service that failed. Several at one branch at the same time usually mean that. Raise it with support, with the time and the branch.
How to check for GPS mocking
- Go to Attendance › Tools & Reports and open GPS Mock Report. It opens on today.
- Set the date range, for example the last month.
- Use Search Employees to look at one person.
- Read each row: Employee Name with Email, Date, Time, Phone Brand, Phone Model and Phone Platform.
- Select Export, then Microsoft Excel (.xlsx), to keep a copy.
Each row is one time the mobile app reported that the phone's location was being faked, for example by a mock-location app.
What Happens Next
These reports only read data. Nothing changes when you open them.
A failed check-in leaves the day without that timestamp. Until someone corrects it, the day can show as tardy, absent or invalid on the Timesheet, and that flows to pay. So each error usually ends in one of three places:
- The employee's phone or habit → talk to them, or use Timekeeping Health to ask them or reset their Face ID.
- A device or a site → check the tablet in Device Monitoring, or the signal at the check-in spot.
- A missing timestamp → the employee files an amendment. See Correcting attendance.
Tips
- Look weekly, not after payroll. A failing device produces missing taps, missing taps produce absent days, and absent days produce a pile of amendments.
- Read errors by branch and by person. The same reason at one branch on one morning is a site problem. The same reason for one person every day is a person or phone problem.
- Check the app version. Errors that stop after an update were the app, not the person.
- Look for a pattern in GPS mock entries before you raise one. Repeated entries from the same person and phone say more than a single one.
- An empty report is not proof that nothing failed. The app sends its error over the same connection that just failed, so a phone with no signal may never send it.
Troubleshooting / FAQ
Q: Someone says they checked in but the day shows absent. Search for them in Mobile Check-in Errors or Tablet Check-in Errors for that day. If there is an error, the check-in failed. If there is nothing, check the Event List for an offline check-in that has not synced yet.
Q: The report is empty. It opens on today. Widen the date range, then clear Filters.
Q: What does "Failed identification" mean? The tablet could not identify who was in front of it.