CueProX
⌘K

Docsevents

Stopping an event

Ending an event for good — what's preserved and what's cleared.

Stopping an event

Stopping an event definitively marks it as finished. This is different from pausing — there's no resume option after a definitive stop.

How to stop

Click Stop event in the event action bar. A modal appears with two options. Choose Stop definitively.

The event is deactivated immediately. Any open sessions are ended and the crew message history from this run is deleted.

What's cleared and what stays

Cleared: the crew message history from this run. Every message sent in active sessions during this event is removed.

Preserved: everything else. Shows, cues, team notes, cue types, timer settings — all of it stays exactly as it was. The event row remains in the room and can be selected, but it's no longer active.

If you start the event again after a definitive stop, it behaves exactly like a fresh event. No message history, clean state.

Warning

The message history from this run cannot be recovered after a definitive stop. If there's any chance you'll want to review the crew chat — for notes, debrief, or reference — use Pause event instead. A paused event's messages are safe until you either stop it definitively or choose Fresh start on resume.

The event stays in your room

Stopping an event doesn't delete it. The event and all its shows and cues remain in the room. Over time, you'll accumulate historical events — each one a record of a past run with its structure intact.

There's no automatic cleanup. If you want to remove an old event from the room, you can delete it from within the director view.

Multiple events in a room

Stopped events don't count against the one-active-at-a-time limit. A room can hold any number of stopped events alongside its current active or paused event. This makes it practical to keep past event setups around for reference — or to reuse their shows as templates for future runs.

Was this helpful?