Early/late window issues
Resolve check-ins that open too early, close too soon, or fail because of timing rules.
If staff see Early Check-In Detected or Late Check-In Detected, the booking exists, but the current check-in timing rules do not allow that attendee to be registered yet or anymore.
Symptom
- Scanner shows
Early Check-In Detectedand saysThis booking is not yet available for check-in. - Scanner shows
Late Check-In Detectedand saysThis booking is expired for check-in. - The event builder warns about invalid check-in timing while you configure the activity.
How the window works
Early Check-in Window (minutes)opens check-in before the slot start.Check-in End Date Calculation Methoddecides when check-in closes.- If you use
Slot end date, check-in stays open until the slot ends. - If you use
personalized, the close time depends onLate Check-in Window (minutes)after the slot start.
Manual override is available
When the scanner detects an early or late arrival, it can still show Continue Check-In. Use that only when your on-site process allows an exception.
Match the symptom to the fix
| What you see | Most likely cause | What to change |
|---|---|---|
Early Check-In Detected / This booking is not yet available for check-in | Staff are trying to check the attendee in before the early window opens. | Wait until the window opens, or increase Early Check-in Window (minutes) if earlier arrivals should be allowed. |
Late Check-In Detected / This booking is expired for check-in | The late window is too short, or the slot has already ended. | Increase Late Check-in Window (minutes), or switch to Slot end date if check-in should remain open until the session ends. |
| The timing feels wrong even though the settings look reasonable | The slot start time or timezone is not what the team expects. | Recheck the slot time, campaign timezone, and the device you are testing with before changing the window rules. |
Builder messages to watch for
-
Activity "{{activity_name}}" uses custom check-in end method but no late window is configuredFix:
Go to Build > Touchpoints > {{activity_name}} > Slots > Check-in Settings and configure the late check-in window -
The total check-in window (early + late) must exceed the slot duration plus buffer time to prevent overlapsPractical fix: review the early window, late window, slot duration, and buffer together before saving.
-
Early and late check-in windows cannot both be 0 in custom mode.Practical fix: if you keep
personalized, set at least one window above0. Otherwise switch toSlot end date. -
In custom mode, at least one check-in window must be greater than 0.Practical fix: set an early or late window, or use
Slot end dateinstead ofpersonalized.
Related
Configure check-in (Self vs. Scan)
Review the check-in method, timing windows, and end-date rule that control when check-in is allowed.
Scanner app access
Fix URL, password, camera, browser, and connectivity issues before you troubleshoot timing.
Event validation errors
Look up the other common event-specific validation messages you may see while configuring check-in.
Check-in rates & no-shows
Measure whether timing changes improve real attendance after the event goes live.