In some situations, viewers who join immediately when a broadcast begins may briefly see content from a previous test stream or earlier broadcast.
This occurs when cached stream segments are temporarily served before the first live source is pushed to the broadcast.
Why This Happens
This typically occurs when:
A test stream was run within the previous 24 hours
The broadcast is started but no source is pushed live immediately
Viewers join before the first live source is added
Once the first source is pushed live, the correct broadcast replaces the cached segments.
Viewers joining after the stream is fully live will not experience this behaviour.
Recommended Start Workflow
To avoid cached content appearing:
Prepare your broadcast and join the Greenroom
Click Go Live
As soon as the Go Live button disappears, immediately push your first source live
You do not need to wait for the End Broadcast button before adding sources.
Best Practices
Push your first source live immediately after Go Live
Avoid delays between starting the broadcast and adding your first source
If you recently ran a test stream, consider waiting 25 hours before your live event
If Cached Content Appears
If cached content briefly appears when a broadcast starts, viewers can refresh the page to immediately load the new live stream. Otherwise, once new live segments are generated, the player will automatically move to the current broadcast within a few seconds.