Event States and Lifecycle

Understand offline, preflight, live, stopping, recovery, and post-event states.

Written By 4ALL.LIVE

Last updated 12 days ago

Understand offline, preflight, live, stopping, recovery, and post-event states.

Best for: Organization administrators, event producers, live operators, and authorized support staff.

Before you start

Event access and actions depend on organization role, team scope, plan entitlements, limits, and current event state.

  • Use an individual verified account in the correct organization and team.
  • Confirm the event owner, live operator, output owner, and incident authority.
  • Review the current configuration before changing an existing or live event.

Reference

  1. Offline. Configuration is available but no active session owns live devices/provider/output state.
  2. Preflight. Readiness checks inspect configuration and runtime dependencies before air.
  3. Starting. The host acquires session ownership and providers/outputs initialize; avoid competing actions.
  4. Live. Usage and caption processing are active; monitor audio, captions, outputs, viewers, and ownership.
  5. Stopping. The system closes providers/outputs and persists state; wait for completion.
  6. Recovery. After disconnect/crash, determine whether the event is still live before restarting anything.
  7. Takeover. An authorized operator assumes ownership of an already-live event when policy allows.
  8. Offline/post-event. Confirm outputs stopped, preserve evidence, and generate approved deliverables.

Use this reference to confirm: The event reaches the intended saved or live state, and every required operator can verify the result without receiving unnecessary access.

Validation checks

  • Operators can identify the authoritative state and choose Go Live, reconnect, observe, take over, stop, or wait correctly.

Compatibility notes

UI says live after operator disconnect

Reopen Live Setup, inspect active-session ownership and audit, then recover/take over by policy.

Stuck stopping

Wait for state resolution, verify network, and escalate with event/session IDs and logs.

Two operators disagree

Use server event state and audit history, not local assumptions.

Limits and cautions

  • Never click Go Live repeatedly during a transition.
  • Takeover and Stop require explicit authority.
  • Do not clear transcript/history as a generic recovery step.