Edge cases

The odd situations, and what happens in each.

Two people, one last spot

  • If two people grab the last spot at the same moment, one gets it and the other is told it just filled.
  • If you add spots while people are signing up, their page may take a moment to catch up.
  • The same email can't sign up for the same slot twice, but it can take a different slot.

Multi-day events

  • Each date is its own occurrence. When you change one day's time, check you're editing the right date.
  • Switching between single-day and multi-day after people have signed up can leave signups on the wrong date. Check the list and email people if you do it.

Time zones and calendars

  • A daylight saving change can shift the time people in other regions see. Check the calendar link if your event is near one.
  • .ics files and Google Calendar links are written in UTC, so each calendar app shows them in its own local time.

Emails

  • Confirmations and reminders can land in spam. Ask people to check there and mark them as not spam.
  • If nobody has signed up yet, sending a reminder tells you so instead of sending nothing quietly.

Spam protection and rate limits

  • Some steps ask for a quick robot check (Cloudflare Turnstile).
  • Lots of submissions from one connection in a short time get “Too many requests” and a note on when to try again.

Editing after you share

  • Changing times or slot names updates the public page right away, so tell the people already signed up. Edit from your dashboard.
  • Cutting spots below the number already signed up doesn't remove anyone. Sort it out in the people list on your dashboard.

Tip: for anything that really matters, stop changing slots a day or two out, and email everyone once with the final plan.