Skip to content

Scan History

Track every QR code scan at your event with detailed records, sync status, and search capabilities. This screen helps you verify attendance, troubleshoot scanning issues, and confirm all guest data has reached your server.

How to get there: Event Dashboard > Scanner > Scan History

Your scan history displays every guest who’s been checked in. Each record shows:

  • The ticket ID that was scanned
  • When and where the scan happened
  • Whether the data is synced (uploaded to server) or still pending
  • How many people were associated with that ticket

All scans appear in reverse chronological order — most recent first.

  1. Tap the search field at the top of the history list
  2. Enter any of these details:
    • Ticket ID (the unique code that was scanned)
    • Scanner name (which device or staff member scanned it)
    • Location (entry gate, hall name, etc.)
  3. Results update instantly as you type

Use the filter chips below the search bar to view:

  • All — Every scan you’ve recorded
  • Synced — Scans successfully uploaded to Velora’s servers ✓
  • Unsynced — Scans waiting to upload (usually syncs automatically)

The statistics row shows your totals:

  • Total Scans — All QR codes checked
  • Synced — Successfully uploaded
  • Pending — Awaiting sync (usually uploads within seconds on good connection)

Each card in your history shows:

DetailWhat It Means
Ticket IDThe unique identifier for this guest’s ticket
LocationWhere the scan happened (gate, entry point, etc.)
ScannerWhich device or staff member performed the scan
PeopleNumber of guests associated with this ticket
Scanned TimeExact timestamp of when the check-in happened
Validation TimeHow long the QR code took to process (in milliseconds)
Synced/Pending badgeGreen checkmark = uploaded; Orange clock = waiting

Normally, scans sync automatically to Velora’s servers. If you want to force a sync:

  1. Tap the sync icon (circular arrows) in the top-right of the app bar
  2. Wait for the green success message
  3. Your history refreshes with the latest sync status

If sync fails (red error message), check your internet connection and try again.

Tap the refresh icon (circular arrow) in the top-right to reload your scan list. Use this if:

  • You just finished scanning and want to see the latest status
  • Sync status hasn’t updated after a few seconds
  • You suspect data is out of sync with the server

If you see “No scan records found”:

  • You haven’t scanned any QR codes yet — tap Start Scanning to begin
  • Your search or filter is too specific — try clearing the search field or selecting All
  • All guests have been checked in and synced out of your current filter view
Your SituationRecommended Next Step
Scans are all synced ✓Download attendance report
Some scans stuck as “Pending”Ensure good WiFi/mobile data; wait 2-3 minutes
Need to verify a specific guestUse search to find their ticket ID
Want to share who attendedExport guest list
Scanning was slow or laggyCheck device internet; reduce background apps
  • Getting Started with QR Code Scanning — How to set up your first scanner
  • Attendance Reports — Export and analyze check-in data
  • Guest Management — Add and organize guests before scanning
  • Troubleshooting Scanner Issues — Fix scanning errors
  • Event Dashboard Overview — Explore all event management tools
  • Syncing & Offline Mode — How Velora handles data when offline

“Sync failed: Check connection” — Your device has lost internet. Verify WiFi or mobile data is active, then tap the sync button again. Scans stay stored locally until synced.

“No scan records found” (when you know you scanned) — Wait 5-10 seconds and tap refresh. If still empty, the scanner app may not have completed the check-in. Try scanning again.

Validation time is very high (>5000ms) — The device or server is slow. This doesn’t affect the guest check-in — they’re still marked as present. Check your internet speed.

Some guests show “Pending” hours after the event — Rare connectivity issues prevented sync. Tap the manual sync button or turn WiFi on/off to trigger sync again.

Duplicate entries for the same guest — The ticket was scanned twice by accident. Both records are valid attendance entries. Review the timestamps to identify the erroneous one.

“Backend ID” missing on a record — Scan succeeded locally but hasn’t synced to servers yet. Check sync status and manually trigger sync if needed.