v1.13.0

Released 16 October 2026: booking waitlists, a daily guide in the Event Host App, one ongoing booking per Activity, and duplication of valid campaigns only.

Released 16 October 2026.

Check before your next publication

Duplicating a campaign: a campaign with validation errors can no longer be duplicated. If you copy an older campaign to start a new one, open it and fix its errors first. Saving it as a template still works.
Several bookings per participant: people can hold only one upcoming slot per Activity at a time, as a booking, a waitlist place or an invitation. A Maximum bookings per participant above 1 now counts past slots. Check Activities where people book several slots ahead.
Integrations that read bookings: people on a waitlist are no longer bookings, so the WAITLIST status no longer appears and ticket.waitlisted.v1 is never sent. See Booking API and Event reference.

Platform

Only a campaign without errors can be duplicated. Duplicating stops with "This campaign can't be duplicated" when the original has validation errors. Warnings don't block a copy, and saving the campaign as a template works whatever its errors. See Duplicate a campaign within an organisation.

Waitlist numbers are in Bookings. The dashboard's Waitlisted Tickets now shows only tickets waitlisted before this release: people who join a waitlist aren't counted in it. Find them in Participants > Bookings > Waitlist Entries. See What OmniLab measures.

3D Models pages load again. Changing page in 3D Models, or in the 3D model picker, left the list loading. It now shows that page. In Studio's lists, choosing a sort no longer clears the filter, and the reverse. See Gamification badges.

Games

Memory shows a loading message. Until every card is ready, players see Loading.... Change the text in Campaign Translation. See Memory.

Events

Waitlists for full slots. A ticket with Limited capacity can have a Waitlist, with its own size. Choose whether a freed place books the next person at once, with Immediate confirmation, or is offered with a time to accept, with Invitation required. Spot allocation decides who gets it: Manual, Queue order or Maximize occupancy. An optional Waitlist Message shows to people while they wait. See Set up a waitlist.

Freed places go to the waitlist first. While people wait for a slot, places freed in it are kept for them, even with Manual. Cancelling a booking gives the place to the waitlist, not back on sale. Attendees see a full slot with waitlist room in orange. From the event page, they can withdraw, or confirm or refuse an offered place. See What happens when a place frees up.

Two waitlist emails. Waitlist Joined is needed to publish an Activity with a waitlist, and Waitlist Invitation when a ticket uses Invitation required. Someone who gets a place receives the usual Booking Confirmation. Through Cheetah or Custom Email Provider, the invitation adds Confirm Booking and Refuse Booking buttons. See Turn on the waitlist emails.

A Waitlist Entries tab in Bookings. In Participants > Bookings, Waitlist Entries shows who waits for each slot. Promote people into freed places, remove them, or download the list. People waiting have no booking, so they aren't in All Bookings, Performance or the bookings file. All Bookings also gets a Refresh button. See Manage the waitlist.

Publishing checks waitlists. Publishing stops when a waitlist has no size, a size too small for one person's request or above twice the capacity, or when its ticket has no Limited capacity. On a published Activity, Studio warns before a change affects people already waiting or invited. See Event validation errors and Change a live waitlist.

One ongoing booking per Activity. Someone with a booking, a waitlist place or an invitation for a slot that hasn't ended can't book another slot of the same Activity until it ends. See How the limits work.

A past booking can't be cancelled. Once a booking's slot has ended, Cancel Booking fails with SLOT_ALREADY_ENDED. A booking cancelled twice at the same moment no longer frees its places twice and overbooks the slot. See Cancel a booking.

A daily guide in the Event Host App. The first time a device opens the app each day, hosts go through a one-minute Usage guide, ticking a box on each screen. Usage guide, at the top of every screen, and the round ? button replay it. See Go through the daily guide and Event Host App access problems.

Transactions

The Receipt Host App guide asks for a tick on each screen. On its daily showing, each screen of the Guide d'utilisation has a Je confirme avoir lu… (I confirm I've read…) box. Commencer, Suivant and C'est parti work once it's ticked. A guide opened again by hand has no boxes. See Review receipts in the Receipt Host App.

Integrations

Salesforce Marketing Cloud: update your templates. Before a campaign uses a waitlist, your Marketing Cloud team must send Waitlist Joined and Waitlist Invitation from the journey, and add the confirm and refuse buttons to the invitation template. Until then, invited people can confirm only from the event page. The Winner template can also show a Download button for a link prize, once it's updated. See Update your Salesforce Marketing Cloud templates.

Developers

Joining a waitlist sends no webhook. Ticket waitlisted (ticket.waitlisted.v1) is never sent, and joining or leaving a waitlist sends no event. A place given from a waitlist arrives as booking.created.v1 and ticket.confirmed.v1. See Event reference.

Booking API: no waitlist status, and two refusals. People on a waitlist have no booking, so the API doesn't return them, and WAITLIST is no longer a status. They appear as CONFIRMED once they get a place. Cancelling a booking whose slot has ended returns 400 with SLOT_ALREADY_ENDED. A busy slot returns 409 with BOOKING_RETRY_REQUIRED: retry after a moment. See Booking API.