Early and late check-in problems
Fix check-ins that open too early, close too soon, or show the wrong time.
Check-in opens Early Check-in Window (minutes) before a slot starts. It closes at the slot end with Slot end date, or a set time after the start with personalized. With personalized, a 14:00 slot with a 15-minute early and a 10-minute late window checks people in from 13:45 to 14:10.
The Host App says "Early Check-In Detected"
Why this happens: the attendee arrived before check-in opened.
On the day: if your team allows it, select Continue Check-In to let them in.
For later sessions:
- Raise Early Check-in Window (minutes) under Slots > Check-in > Advanced Check-in.
- Save, then publish the campaign again.
The Host App says "Late Check-In Detected"
Why this happens: the attendee arrived after check-in closed.
On the day: if your team allows it, select Continue Check-In.
For later sessions:
- Raise Late Check-in Window (minutes), or choose Slot end date.
- Save, then publish the campaign again.
Check-in opens at the wrong time
Why this happens:
- Slot times follow the timezone shown on each Date field, such as Date (Europe/London).
- The campaign's timezone differs from where the event runs.
Fix it:
- In the Activity's Slots tab, check the timezone on the Date field.
- If it's wrong, correct the campaign timezone in Build > General.
- Check the slot's start time, then both windows.
Publishing is blocked: "uses custom check-in end method but no late window is configured"
Fix it: set Late Check-in Window (minutes) above 0, or choose Slot end date.
Studio warns about "a very large early check-in window"
This appears when the early window is 60 minutes or more. It doesn't block publishing: check the value is intended.
Still stuck?
Contact your Customer Success Manager. Send the campaign and Activity names, the slot time, when the attendee arrived, and the message shown.