4All Status, Health, and Connection State Reference

Interpret common event, preflight, WebSocket, desktop, encoder, XPression, ASL, and output states.

Written By 4ALL.LIVE

Last updated About 1 month ago

Translate UI state labels into the next safe operator action instead of guessing or restarting healthy components.

Best for: Operators, producers, support, and implementation engineers.

Before you start

Some detailed diagnostics require team admin, desktop, or internal support access.

  • Use the current production release and approved organizational policy.
  • Record resource IDs, exact time zone, and accountable owner.
  • Validate in a non-production environment when possible.
  • Identify which component owns the state.
  • Record the exact label, timestamp, event/output, and last state transition.
  • Use the component-specific article for remediation.

Reference

  1. Event Offline means the event is not currently live; verify schedule/setup before starting. Live means production processing is expected.
  2. Preflight Passed means blocking checks passed; Warning means advisory or recoverable concerns; Error/Critical means a required check failed; Skipped means the check did not run.
  3. WebSocket Connecting is an in-progress handshake; Connected/Open means transport is available; Disconnected/Closed means it ended; Error means the connection failed—inspect code/reason and network.
  4. Desktop local STT Idle → Connecting → Connected → Running is normal; Error requires sidecar/audio/model inspection.
  5. Encoder Stopped → Starting → Running → Stopping is normal. Target Idle → Connecting → Connected may change to Reconnecting or Failed.
  6. XPression runtime should show cloud connection, output running, last caption/sequence, latency, local URLs, and errors; distinguish cloud input from local output connectivity.
  7. ASL Offline/Waiting/Ready/On air describe interpreter/control readiness; do not go on air until the approved ready conditions pass.
  8. Billing/license messages are authorization/capacity states, not network failures.

Use this reference to confirm: The operator identifies the owning layer and follows the smallest relevant recovery path.

Validation checks

  • State transition is timestamped.
  • Local and receiver state are compared.
  • No unrelated healthy layer is restarted.
  • Recovery article is linked in the runbook.

Compatibility notes

  • Stuck transitional state: wait the documented timeout, then capture logs before retry.
  • Connected but no content: transport is healthy; inspect source/event/language.
  • Failed immediately: inspect configuration/authentication.
  • Repeated reconnect: inspect network/destination rather than event content.

Limits and cautions

Important: State labels can evolve by release. Capture the exact build and screenshot and confirm current UI before publishing this reference.