The Info log records what the kiosk did between scans: a participant's card being read, them
confirming or declining their details, the assignment being saved, and the kiosk starting up. Where the
Transponder log is about the chip, Info is about the person
standing at the kiosk.
Columns
| Column | Shows |
|---|
| Local Time | When it happened, in your time zone. |
| Status | What happened (below). |
| TransponderID | The transponder involved, once there is one. |
| UID | The ID from the participant's card or QR code. |
| Session | The kiosk sitting it belongs to — see View Sessions. |
Status values
| Status | Meaning |
|---|
UID_FOUND | A card was scanned and the participant was found. (Older logs say FOUND.) |
UID_NOT_FOUND | A card was scanned but no participant has that ID. |
DUPLICATE_UID | More than one participant has that ID. |
INFO_CONFIRMED | The participant confirmed the details on screen were theirs. |
INFO_DECLINED | The participant said the details were not theirs. |
ASSIGNMENT_SUCCESS | The transponder was saved to the participant. Its Details include how long the whole assignment took. |
ASSIGNMENT_ERROR | The transponder could not be saved to the participant. |
MAX_ATTEMPTS | Too many failed scans in a row; the kiosk gave up on this participant. |
SESSION_START | The kiosk began a new session. |
Using it
- A run of
UID_NOT_FOUND usually means the kiosk's UID Field setting names the wrong field, or the participants have not been imported yet.
- A lot of
INFO_DECLINED can mean the Display Fields are confusing people.
ASSIGNMENT_ERROR usually means the Update API key cannot write to the event.- For timings built from these rows, see Process.