Event validation errors

Common reasons an event blocks publishing and how to fix them.

Your event won't publish, and the message points to an event-specific problem. Below are the most common causes by area, each with a plain-language fix you can apply yourself.

Booking notifications

  • Booking confirmation email is missing — when booking is enabled, attendees must receive a confirmation. Open Build > Notifications > Booking Confirmation and enable it globally or for this activity.
  • Booking cancellation email is missing — recommended when attendees may cancel. Enable Booking Cancellation globally or per activity.
  • Reminder is on but cancellation email is off — when reminder emails are active, the cancellation email must also be on. Enable Booking Cancellation so attendees are informed if their booking changes after a reminder goes out.

Slots and dates

  • Two specific dates overlap — open Slots > Dates > Specific Dates and adjust the conflicting sessions so each one ends before the next starts.
  • Two weekly time ranges on the same day overlap — open the affected weekday in Slots > Dates > Weekly and separate the overlapping ranges.
  • A slot falls outside the campaign dates — check Slots > Dates > Specific Dates and move the slot inside the campaign window, or extend the campaign dates.
  • Slot division is on but no dates are set — set at least one date before turning on Divide into Slots.

Tickets and capacity

  • No ticket types configured — open Slots > Tickets and add at least one ticket type for the bookable activity.
  • A ticket has no display name — open the ticket in Slots > Tickets and enter a name attendees will see.
  • A ticket's capacity is zero — set a capacity above zero so the ticket can be booked.
  • Limit Availability is on but no sale dates are set — fill in both Availability Start Date and Availability End Date in the ticket settings.
  • Sale start date is after sale end date — make sure the start date is earlier than the end date.
  • Per-contact limit exceeds total capacity — lower the per-contact booking limit to be at or below the total ticket capacity.

Check-in setup

  • Early check-in window is negative — set the early window to zero or a positive number in Slots > Check-in.
  • Late check-in window is negative — set the late window to zero or a positive number.
  • Check-in form is on but no template is selected — choose a form template in Slots > Check-in.
  • Custom check-in end method but no late window — when using the custom end method, add a late window value so OmniLab knows when check-in closes.

Booking restrictions and special event modes

  • Booking limit per contact is set to zero — enter a positive number for the per-contact booking limit, or turn the booking limit off.
  • Validation codes restriction is on but no pool is selected — choose a validation codes pool or remove the restriction.
  • Check-In Only mode needs exactly one technical ticket — open Slots > Tickets and make sure there is exactly one technical ticket configured.

Notices that don't block publishing

Some results are reminders rather than errors. A notice about a large early check-in window or a check-in form requirement is a prompt to review your setup, not a blocker. Read it, confirm it matches what you intended, and continue.

Was this helpful?

Optional comments help us improve this page for future authors and readers.

On this page