CueProX
⌘K

Docsevents

Event lifecycle

The four states an event moves through — and what each one means.

Event lifecycle

An event in CueProX moves through four states. Understanding them makes it easier to know which controls are available and what's happening to your data at each stage.

The four states

Idle — The event has been created but never started. Cues and shows exist and can be edited; no session is running. Every new event starts here.

Active — The event is live. A director can start shows, advance cues, and send crew messages. Only one event per room can be active at a time — starting a new event automatically deactivates any other active event in that room.

Paused — The event has been suspended mid-run. Cues, shows, and the crew message history from this run are all preserved. No session is running, but the event is ready to resume. The pause state is designed for genuine breaks — an interval, a long interlude, a building that's locking up between a morning and evening service.

Stopped — The event has been definitively ended. Cues and shows are preserved, but the message history from this run has been cleared. The event row stays in the room but is no longer active or paused.

How states transition

[ Idle ] ──── Start event ────▶ [ Active ]
                                     │
                              ┌──────┴──────┐
                           Pause        Stop definitively
                              │              │
                              ▼              ▼
                          [ Paused ]    [ Stopped ]
                              │
               ┌──────────────┴──────────────┐
           Resume                      Fresh start
               │                             │
               ▼                             ▼
           [ Active ]                   [ Active ]
        (messages kept)            (messages cleared)
  • Start event moves an idle or paused event to active.
  • Pause event suspends an active event without clearing anything.
  • Stop definitively ends an active or paused event and clears the message history.
  • Resume re-activates a paused event with the message history intact.
  • Fresh start re-activates a paused event after clearing the message history.

What changes at each transition

Starting from idle: nothing is deleted. All cues and shows are untouched.

Pausing: the session ends. Crew messages are preserved in the database. You can resume later and pick up the exact same run.

Resuming: the event becomes active again. Depending on the choice — Resume or Fresh start — messages are either kept or deleted before the event reactivates.

Stopping definitively: crew messages from this run are deleted immediately and cannot be recovered. Cues and shows remain.

Note

Idle and stopped events are indistinguishable in the database — both have the same state values. The difference is just where you are in the workflow: an idle event was never run; a stopped event has been. CueProX doesn't need to track which one it is to work correctly.
Was this helpful?