Event validation errors

This page groups the most useful event-specific validation messages you may see while building or publishing an event, plus the exact fixes shown in OmniLab.

Booking notifications

• Message: Activity '{{activity_name}}' has booking enabled but no booking confirmation notification is configured

  Explanation: When activities have booking enabled, participants must receive confirmation emails when they successfully book a slot. This ensures they have proof of their booking and important details about the activity.

  Fix: Go to Build > Notifications > Booking Confirmation and either enable global notifications or configure specific notifications for '{{activity_name}}'

• Message: Activity '{{activity_name}}' has booking enabled but no booking cancellation notification is configured

  Explanation: When activities have booking enabled, it's recommended to send cancellation emails when bookings are cancelled. This keeps participants informed and helps maintain good communication.

  Fix: Consider going to Build > Notifications > Booking Cancellation and either enabling global notifications or configuring specific notifications for '{{activity_name}}'

• Message: Activity '{{activity_name}}' has booking enabled but no booking confirmation reminder notification is configured

  Explanation: When activities have booking enabled, it's helpful to send reminder emails before the scheduled activity. This reduces no-shows and helps participants remember their booking.

  Fix: Consider going to Build > Notifications > Booking Confirmation Reminder and either enabling global notifications or configuring specific notifications for '{{activity_name}}'

• Message: Booking confirmation reminder is enabled but booking cancellation notification is not active

  Explanation: If you send reminder emails to participants, you must also have cancellation notifications enabled. This ensures that if a booking is cancelled after a reminder is sent, participants are properly informed and don't show up for a cancelled booking.

  Fix: Go to Build > Notifications > Booking Cancellation and either enable global notifications or configure specific notifications for all activities with booking

• Event-specific reminder variant: Booking confirmation reminder is enabled for '{{touchpoint_name}}' but no booking cancellation notification is configured

  Explanation: If you send reminder emails for this activity, you must also have cancellation notifications enabled. This ensures that if a booking is cancelled after a reminder is sent, participants are properly informed and don't show up for a cancelled booking.

  Fix: Go to Build > Notifications > Booking Cancellation and either enable global notifications or configure a specific notification for '{{touchpoint_name}}'

Slots and dates

• Message: Activity '{{activity_name}}' has overlapping specific dates: Date #{{date_index_1}} ({{date_1}} {{time_range_1}}) overlaps with Date #{{date_index_2}} ({{date_2}} {{time_range_2}})

  Explanation: Activity time slots cannot overlap as this would create scheduling conflicts for participants.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Dates > Specific Dates and adjust the overlapping time slots

• Message: Activity '{{activity_name}}' has overlapping time ranges on {{day_name}}: Range #{{range_index_1}} ({{time_range_1}}) overlaps with Range #{{range_index_2}} ({{time_range_2}})

  Explanation: Time ranges on the same day cannot overlap as this would create scheduling conflicts.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Dates > Weekly > {{day_name}} and adjust the overlapping time ranges

• Message: Activity '{{activity_name}}' slot #{{slot_index}} ({{slot_start}} - {{slot_end}}) falls outside the campaign dates ({{range_start}} - {{range_end}})

  Explanation: Activity time slots must be within the campaign date range. Slots scheduled outside the campaign dates will not be accessible to participants.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Dates > Specific Dates and adjust slot #{{slot_index}} to be within {{range_start}} - {{range_end}}

• Message: Activity '{{activity_name}}' slot #{{slot_index}} ({{slot_start}} - {{slot_end}}) falls outside the activity dates ({{range_start}} - {{range_end}})

  Explanation: Activity time slots must be within the activity's custom date range. Slots scheduled outside these dates will not be accessible to participants.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Dates > Specific Dates and adjust slot #{{slot_index}} to be within {{range_start}} - {{range_end}}

• Message: Activity "{{activity_name}}" has slot division configured but no dates specified

  Explanation: Slot division requires specific or weekly availability dates to be configured to determine when the activity is available.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Dates and configure either specific dates or weekly availability

Tickets and capacity

• Message: Activity '{{activity_name}}' has booking enabled but no ticket types configured

  Explanation: When booking is enabled, at least one ticket type must be configured to allow participants to reserve their spots.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets and keep at least 1 ticket

• Message: Ticket #{{ticket_index}} in activity '{{activity_name}}' has no display name

  Explanation: Each ticket type needs a display name so participants can understand the different options available.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets > Ticket #{{ticket_index}} and enter a display name

• Message: Ticket '{{ticket_name}}' in activity '{{activity_name}}' has capacity set to 0

  Explanation: Ticket types with zero capacity cannot be booked by participants.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets > {{ticket_name}} and set capacity greater than 0

• Messages:

  • Ticket '{{ticket_name}}' in activity '{{activity_name}}' has limited availability enabled but no sale start date
  • Ticket '{{ticket_name}}' in activity '{{activity_name}}' has limited availability enabled but no sale end date

  Explanation: When limit availability is enabled, both sale start and end dates must be configured.

  Fixes:

  • Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets > {{ticket_name}} and set a sale start date
  • Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets > {{ticket_name}} and set a sale end date

• Message: Ticket '{{ticket_name}}' in activity '{{activity_name}}' has sale start date ({{sale_start_date}}) after or equal to sale end date ({{sale_end_date}})

  Explanation: Sale start date must be before sale end date to create a valid availability window.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets > {{ticket_name}} and ensure sale start date is before sale end date

• Message: Ticket '{{ticket_name}}' allows {{per_contact}} tickets per person but total capacity is only {{total_capacity}}

  Explanation: The per-contact limit should not exceed the total capacity, as this could lead to confusing booking scenarios.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets > {{ticket_name}} and adjust per contact limit

Check-in setup

• Message: Activity '{{activity_name}}' has a negative early check-in window of {{early_minutes}} minutes

  Explanation: Early check-in window cannot be negative as it represents time before the slot starts.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Check-in and set the early check-in window to 0 or a positive value

• Message: Activity '{{activity_name}}' has a negative late check-in window of {{late_minutes}} minutes

  Explanation: Late check-in window cannot be negative as it represents time after the slot starts.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Check-in and set the late check-in window to 0 or a positive value

• Message: Activity '{{activity_name}}' requires a check-in form but no template is selected

  Explanation: When check-in form is required, a form template must be selected to collect participant information.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Check-in and select a check-in form template

• Message: Activity "{{activity_name}}" uses custom check-in end method but no late window is configured

  Explanation: When using a custom check-in end calculation method, you must specify how long after the slot start time participants can still check in.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Check-in Settings and configure the late check-in window

Booking restrictions and special event modes

• Message: Activity '{{activity_name}}' has booking limit enabled but booking limit per contact is {{limited_number}} (must be greater than 0)

  Explanation: When booking restrictions are enabled, the maximum bookings per contact must be a positive number to properly limit how many times a participant can book this activity.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Limited capacity and set a valid positive number for booking limit per contact, or disable the booking limit

• Message: Activity '{{activity_name}}' has booking validation codes restriction enabled but no validation codes pool configured

  Explanation: When the booking validation codes restriction is active, a validation codes pool must be configured so bookings can be checked against the selected pool.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Booking restrictions and select a validation codes pool, or disable the booking validation codes restriction

• Message: Check-in only activity '{{activity_name}}' has no technical ticket configured

  Explanation: Check-in only activities require exactly one technical ticket to manage capacity and check-in flow.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets and ensure exactly one technical ticket is configured

• Message: Check-in only activity '{{activity_name}}' has {{ticket_count}} technical tickets configured

  Explanation: Check-in only activities should have exactly one technical ticket to avoid confusion in the check-in process.

  Fix: Go to Build > Touchpoints > {{activity_name}} > Slots > Tickets and configure exactly one technical ticket

Informational messages you may also see

Some event-specific validation results are there to inform rather than block. Common examples include:

• Activity "{{activity_name}}" allows early check-in {{early_minutes}} minutes before the slot start
• Activity "{{activity_name}}" requires participants to fill a check-in form
• Activity '{{activity_name}}' has a very large early check-in window of {{early_minutes}} minutes

These messages are useful prompts to review the setup, but they do not mean the event is necessarily broken.

Related