Event validation errors

Why an event won't publish, and how to fix each cause.

5 min read

The Publish window lists each error with the Activity it belongs to. Each message names your Activity or ticket: search this page for the words after the name, fix it, then publish again.

An old Activity won't publish

The message starts: Activity '[name]' is a legacy activity and can no longer be published.

Why this happens: a long-running campaign, or one duplicated from it, still has an Activity created long ago. Activities you create today aren't affected. Publishing blocks it so it can't fail when an attendee tries to book.

Bookings, check-ins and reports recorded so far stay with the old Activity. If the event is already taking bookings, talk to your Customer Success Manager before you change anything.

Fix it:

  1. In Build > Touchpoints, select Add New Touchpoint, then Activity.
  2. Set it up with the same details, schedule, tickets and check-in settings.
  3. In Share, get the new link and QR codes.
  4. Replace every link or QR code already printed, scheduled or published.
  5. Remove the old Activity.

For the full setup, see Create an Activity touchpoint.

Booking emails

  • "has booking enabled but no booking confirmation notification is configured": in Build > Notifications, turn on Booking Confirmation, globally or for this Activity.
  • "Email banner image is missing for … notification": upload an Email Banner in that notification.
  • "Booking confirmation reminder is enabled but booking cancellation notification is not active": turn on Booking Cancellation too.
  • "has a waitlist but no Waitlist Joined notification is active": in Build > Notifications, turn on Waitlist Joined, globally or for this Activity.
  • "has a waitlist that requires an invitation but no Waitlist Invitation notification is active": turn on Waitlist Invitation the same way.
  • "no email marketing addon (Cheetah, Salesforce Marketing Cloud or Custom Email Provider) is active": turn one on in Build > Settings > Advanced Settings > Addons.
  • "More than one email marketing addon": keep only one of Cheetah, Salesforce Marketing Cloud and Custom Email Provider on.

See Configure booking notifications.

Dates and slots

  • "has no dates configured": add at least one weekday or specific date.
  • "has end time (…) before start time (…)": check each date and weekly range.
  • "has overlapping specific dates" or "has overlapping time ranges": see Overlapping slots.
  • "falls outside the campaign dates" or "falls outside the activity dates": move the slot inside those dates, or extend them.
  • "has a negative slot duration" or "has a negative buffer time": set both to 0 or more.
  • "has slot division configured but no dates specified": add a date, or turn off Divide into Slots.
  • "is corrupted and needs to be replaced": a copied date carries a hidden fraction of a second. Delete it and add it again: see Replace a corrupted slot.

Tickets and capacity

  • "has booking enabled but no ticket types configured": add a ticket in Slots > Tickets.
  • "has no display name": enter the ticket's Display Name.
  • "has capacity set to 0" or "has negative capacity": enter a positive Total capacity.
  • "has negative per contact limit": enter a positive number, or turn the limit off.
  • "tickets per person but total capacity is only": lower Maximum capacity per contact.
  • "has limited availability enabled but no sale start date", or no sale end date: fill both dates under Limit Availability.
  • "has sale start date (…) after or equal to sale end date": make the start date earlier than the end date.

Waitlist

A ticket's waitlist settings are in the Activity's Slots > Tickets.

  • "has a waitlist but no limited capacity": turn Limited capacity back on for that ticket, or turn its Waitlist off.
  • "has a waitlist with no size": enter a Waitlist size (seats) of 1 or more.
  • "seats one visitor can request": raise Waitlist size (seats) to the number in the message, or lower Maximum capacity per contact.
  • "more than twice its capacity": lower Waitlist size (seats) to twice the Total capacity or less.

Check-in

  • "has a negative early check-in window" or "has a negative late check-in window": set it to 0 or more.
  • "requires a check-in form but no template is selected": choose a template, or turn off Check-in Form.
  • "uses custom check-in end method but no late window is configured": set a Late Check-in Window (minutes) above 0.
  • "has no technical ticket configured" or "technical tickets configured": contact your Customer Success Manager. Studio doesn't show this ticket.

Activity messages

  • "has no Booking Confirmation Message", "has no Check-in Confirmation Message" or "has no Message If Event Ended": in the Activity's Slots > Messages, write that message in at least one language. Booking Confirmation Message is needed only when the Activity takes bookings.

Restrictions

  • "has booking limit enabled but booking limit per contact is 0": enter a number above 0, or turn off Limit bookings per participant.
  • "has booking validation codes restriction enabled but no validation codes pool configured": choose a pool, or turn it off.

People already booked or waiting

When you publish changes to a live Activity, Studio checks how they affect people who have already booked or joined the waitlist.

  • "could not be checked": the check didn't go through, so publishing is blocked. Validate again in a few moments. If it keeps failing, contact your Customer Success Manager.
  • "more than the new waitlist size": some slots already have more seats waiting than the new size. Raise Waitlist size (seats) to the number in the message, or first promote or cancel people: see Manage the waitlist.

Messages that don't block publishing

Warnings and suggestions are advice. Studio flags, for example, a missing cancellation or reminder email, an early window of 60 minutes or more, or tickets mixing limited and unlimited capacity. On a live Activity, it also warns that turning a waitlist off, switching from Invitation required to Immediate confirmation or changing Spot allocation moves nobody by itself: people already waiting or invited keep their place. Check each one is intended, then publish.

A badge is optional: an Activity publishes without one.

Next steps

On this page