Go Live and Stop Safely

Start and end the authoritative live session with communication, verification, and recovery discipline.

Written By 4ALL.LIVE

Last updated About 1 month ago

Start and end the authoritative live session with communication, verification, and recovery discipline.

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.

Step by step

  1. Final readiness call. Confirm host, audio, provider, languages, outputs, preflight, downstream returns, usage, and backups.
  2. Announce Go Live. Use the production communication channel and identify the event.
  3. Select Go Live once. Wait through the starting transition.
  4. Verify on air. Confirm live state, fresh source captions, translations, required outputs, viewer, and downstream program.
  5. Monitor. Watch audio, caption freshness, providers, outputs, viewers, ownership, and audit.
  6. Prepare stop. Announce the order for ASL/desktop/stream/graphics/session stops.
  7. Select Stop once. Wait for offline confirmation and output clearing/holding behavior.
  8. Post-stop checks. Verify no encoder/bridge/output remains active, preserve logs, and begin approved exports.

What success looks like: The event reaches the intended saved or live state, and every required operator can verify the result without receiving unnecessary access.

Check your setup

  • The event transitions once to Live with verified outputs and once to Offline with dependent processes closed.

Troubleshooting

Go Live blocked

Resolve the displayed preflight/entitlement/ownership issue.

Button clicked twice

Stop interacting and inspect server state/audit before any recovery.

Stop does not complete

Maintain communication, inspect network/session state, avoid restarting outputs blindly, and escalate with IDs/logs.

Security and operational notes

  • Only the authorized cue owner starts/stops.
  • Stop is not a substitute for downstream verification.
  • Do not clear transcript to fix state.