Production Truck: Recovery and support

Recovery and support

• A disconnected controller reconnects to the authenticated managed engine. Reopening the controller leaves the active OBS process and its outputs intact. A running process is not duplicated even when OS policy prevents reading its ownership marker; maintenance then requires stopping it from OBS.
• If the owned OBS process exits, the supervisor backs off and relaunches it. Three exits within ten minutes require a manual retry. An OBS crash does not automatically resume streaming, recording or replay; review the new program and readiness before going live.
• Stale/disconnected status is shown as OUTPUT UNKNOWN, and controls are disabled. The application never replays a queued output command after reconnection. Hub outage reporting contains state only.
• Corrupt station/startup settings are preserved as recovery files rather than deleted; the UI identifies the recovery. Private OBS workspace files remain available for engineering repair.
• Download support report exports configuration checks, OBS version/profile/collection, current output state and recent operation names/statuses. Camera URLs, pairing tokens, OBS passwords and stream keys are omitted. Operation logging is best effort and does not turn a successful output action into a failed command when storage is unavailable.
• OBS plugin availability, camera frame continuity, true audio levels, encoder throughput, network delivery and hardware temperature need workstation/event qualification. The application does not claim failover encoding, ISO recording, PTZ, a hardware audio meter or broadcast SLA certification.