What Happens When Something Goes Wrong on Your Stream
A practical look at how playout.video handles stream issues automatically: what recovery looks like, what you'll see, and when (rarely) you actually need to intervene.
Introduction
Things go wrong sometimes. A network blip. A corrupted video file. A platform doing platform things. The question that matters isn't whether something will go wrong, it's what happens when it does and whether you need to do anything about it.
This guide covers exactly that. The kinds of things that go wrong, what playout.video does automatically, and the (rare) cases where you should step in.
The Short Version
For 95% of issues, the answer is: the stream recovers automatically and you don't need to do anything.
For 4%: the stream recovers automatically but you might want to investigate why it happened.
For 1%: you need to step in.
What Recovers Automatically
These are the issues that handle themselves. You'll typically see no impact, or a brief blip viewers may not notice.
A frame in a video is corrupted
What happens: the stream skips the bad frame and continues. Viewers may see a single-frame glitch (1/30th of a second) and that's it.
What you do: nothing.
A network blip while loading the next clip
What happens: the system retries for a few seconds. Most of the time, the retry succeeds before the current clip ends and the transition is clean. If recovery is slow, a black frame plays briefly while the next clip loads.
What you do: nothing.
A video file is briefly inaccessible
Same as above, retry, then fallback.
A platform destination has a momentary issue
What happens: the stream stays live to other connected platforms. The affected destination reconnects automatically.
What you do: nothing, unless multiple destinations are affected (then check the platform's status page).
A guest's connection drops in Live Studio
What happens: the system tries to reconnect them automatically. Their video may freeze briefly.
What you do: keep talking. If they don't reconnect within 30 seconds, switch to a host-only layout.
The underlying server has an issue
What happens: the stream is moved to another server automatically. Calendar progress is preserved.
What you do: nothing. You may not even notice it happened.
What You'll See in the Dashboard
Your dashboard shows a stream status indicator:
Green: stream is healthy
Amber: recovery in progress (usually clears within seconds)
Red: stream is offline or has a sustained issue
If you see amber, no action needed, wait. If amber persists for more than a minute, take a closer look.
If you see red and you didn't intend to stop the stream, that's a case for investigation.
When You Should Investigate
A handful of patterns suggest something deeper is wrong. None of them require panic, but all of them are worth a look.
Recurring amber status
If the dashboard shows amber multiple times per hour, something is consistently triggering recovery. Likely causes:
A video file in your library has corruption that's being repeatedly hit. Check the Media Library for files showing a warning badge.
Your library is on slow storage (rare on playout.video, but possible if you're using external storage paths).
A specific source is unstable (e.g., an RTMP source from a flaky encoder).
Persistent red status
If the stream is offline and won't restart automatically, check:
Are your destinations authenticated? OAuth tokens (especially YouTube) can expire. Re-connect the destination.
Is your library empty? A stream with no content can't run. Add content.
Was the calendar empty? A Scheduled Stream with no calendar blocks won't auto-start. Add a block.
Sudden viewer drop
If your viewer count drops sharply but the stream shows green, it's likely a platform-side issue, not yours. Check the platform (YouTube Studio, Twitch dashboard, etc.) for warnings.
What to Do If You Need to Restart
Most of the time, you don't need to. But if you do:
Click End Live in the toolbar
Wait 10 seconds
Click Go Live
The stream restarts. Calendar position is preserved. Destinations reconnect.
For a Scheduled Stream with auto-start, you can usually just click End Live and let auto-start fire on the next calendar block.
Common Mistakes That Look Like "Stream Issues"
A few things people report as "issues" that are usually configuration:
"My YouTube stream went offline": probably your YouTube destination's OAuth token expired. Re-connect under Destinations.
"My stream is playing the wrong content": check the Calendar. A higher-priority block may have taken over.
"My stream sounds quiet": check audio levels in the source files. The stream plays content at the loudness it was encoded at.
"Viewers say the stream is choppy": check viewer-side, not stream-side. Their internet, their device, their player.
Pro Tips for Reliability
Multistream to multiple platforms. If one platform has issues, the others stay live.
Keep your library clean. Remove or replace files that show warnings.
Re-authenticate destinations periodically. OAuth tokens for some platforms expire on a schedule.
Use the Calendar with auto-start. Less surface area for "I forgot to start the stream" issues.
Subscribe to platform status pages. YouTube, Twitch, Facebook all have status dashboards.
When to Contact Support
Contact support if:
The dashboard shows red and won't recover after restart attempts
You see error messages you don't recognize and can't dismiss
Multiple streams are affected at the same time (suggests a platform-level issue worth verifying)
Most issues never need support. If yours does, please reach out, we'd rather hear about a problem than have you struggle with it silently.