A Switchboard Live stream stuck on “starting” can be failing before video reaches Switchboard, between Switchboard and YouTube, or in YouTube’s event state. Check those stages in order: the Confidence Monitor tells you whether Switchboard is receiving video, while YouTube Live Control Room shows destination-side health and errors.
Do not change every encoder setting at once. A missing incoming feed, a destination that has not started, and a YouTube event that is scheduled are different symptoms; each points to a different next check.
Locate where the stream stops
Think of the broadcast as a route with three checkpoints. First, your encoder sends video to the Switchboard workflow. Next, Switchboard forwards the feed to the selected YouTube destination. Finally, YouTube accepts that feed into the event and makes it live. A “starting” label by itself does not identify which link has failed.
Start on the Switchboard workflow page, not with a broad reset. Is there a picture in the Confidence Monitor? Does the workflow show that it is receiving? Then look at the YouTube destination status, and open the event in Live Control Room to read its health indicator and any timestamped error. Write down what each screen says before changing anything; this makes it easier to tell whether a change helped.
| What you see | Likely stage to investigate next | Useful next check |
|---|---|---|
| No picture and “Not Receiving” | Encoder to Switchboard | Compare the encoder’s server address and stream key with the selected workflow |
| Picture and “Receiving”, but the YouTube destination is not live | Switchboard to YouTube, or the event state | Check the destination status and the matching YouTube event |
| YouTube shows an error beside its Health Indicator | YouTube ingest or event | Use the specific error and its timestamp, rather than resetting unrelated settings |
| YouTube schedules the stream instead of going live | Event or template configuration | Check whether the active Switchboard template has a title |
These are diagnostic clues, not guarantees about the cause. For example, a picture at Switchboard confirms that the encoder feed has reached that point; it does not prove that YouTube accepted the stream or that viewers can see it. Likewise, a destination that looks active in one screen is not a substitute for checking the event’s Live Control Room status.
If you run a continuous playlist from OBS, a file or source issue can also matter before the feed reaches Switchboard. For the playback side, see this guide to looping nature footage in OBS; use it to check the source rather than assuming it explains a YouTube destination error.
Check encoder status and stream URL/key
If the workflow says “Not Receiving” or the Confidence Monitor has no picture, check the encoder first. Confirm it is actually streaming, and that it is using the Stream URL and Stream Key shown for the exact Switchboard workflow you intend to use. A key copied from another workflow, an old destination, or a previous setup can send the encoder somewhere else.
In Switchboard, reveal the key if needed and compare it character by character with the encoder configuration. Also compare the server or URL, not just the key. Avoid posting a stream key in screenshots or public support requests: anyone with access to it may be able to send a feed to that ingest point. If you suspect it has been exposed, use the appropriate stream-key controls to replace it, then update the encoder with the new value.
Start or resume the encoder output and allow a moment for the workflow to register an incoming signal. Switchboard’s initial setup guidance describes a test feed that should change the workflow from “Not Receiving” to “Receiving” when video arrives. This test checks the connection from the encoder to Switchboard; it does not, by itself, put the YouTube destination live. See Switchboard’s initial setup guide for its workflow-specific steps.
If the encoder reports an error as it starts, follow the error rather than continuing to click the destination Start button. YouTube’s troubleshooting guide for live streams advises using the latest encoder version, checking the encoder output, and examining CPU load and the outbound connection. A local recording, if you have one, can help establish whether the video itself looks right before it is sent.
An encoder can also be running without producing the feed you expect. Check its output preview and any error messages, then verify that it is sending to the intended workflow. If a local recording plays properly but the workflow never receives video, focus on the destination address, key, and outbound connection rather than rebuilding the video file immediately.
Confirm video in the Confidence Monitor
The Confidence Monitor is the practical boundary between the encoder and the rest of the route. It previews the video currently arriving from the encoder. If it shows a no-source state, YouTube destination troubleshooting is premature: Switchboard has not yet confirmed an incoming picture to forward.
When video does appear, check more than the presence of a single frame. Look for an ongoing picture and, where shown, the incoming bitrate and frame rate. Those readings can help distinguish a stable feed from one that appears briefly and then stops. They are observations about the incoming signal, not proof that every setting is correct or that YouTube will accept it.
Switchboard recommends constant bitrate (CBR), a two-second keyframe interval, and 30 or 60 frames per second in its initial setup guidance. Treat those as its stated recommendations, not as a universal cure for a stream that will not start. Change a setting only when the encoder output or a specific YouTube error gives you a reason. If you adjust one value, note the original first so that you can reverse the change if the result is worse.
Once the monitor shows the intended video and the workflow reports “Receiving,” use the workflow’s YouTube destination controls. Switchboard’s setup guide explicitly distinguishes this input test from going live to a destination. That distinction matters: the encoder-to-Switchboard link can be working even while the separate destination launch is not.
If the monitor shows the wrong scene, a black frame, or a source that ends quickly, correct that at the encoder or playback source before investigating YouTube. A looping media setup has its own failure modes; this guide to continuous YouTube playback from VLC may help if the source is a podcast or other file-based programme.
Check the YouTube destination state
If Switchboard is receiving the right picture but YouTube is not live, check that the destination is the intended YouTube channel and event. Confirm which event the workflow is targeting, and whether the destination is still waiting to start, reports an error, or shows as connected. A successful encoder test does not mean the destination has already been launched.
Use the controls in the active workflow to start the destination only after the incoming feed is present. If a Start control is unavailable, return to the workflow status rather than trying to force the event from several places. Switchboard’s workflow documentation describes destination controls in the context of an incoming signal; the workflow page guide can help you identify the relevant status and controls.
Then check the corresponding event in YouTube Studio or Live Control Room. Make sure you are looking at the event associated with this stream, not a different scheduled broadcast on the same channel. If there are multiple test events or workflows, match the title and event details before deciding that YouTube has failed to receive the feed.
A particular scheduling symptom has a documented template check: Switchboard’s FAQ says that an active template without a stream title may result in YouTube scheduling streams instead of going live. If YouTube is scheduling the event rather than starting it, stop the stream as advised in the FAQ and update the YouTube title field in the active template. This is a specific possibility for that symptom, not an explanation for every “starting” delay or missing feed. See the Switchboard FAQ for the narrow case.
Inspect YouTube Live Control Room health
Open the event’s Live Control Room and read the Health Indicator and any error messages next to it. YouTube says the dashboard displays timestamped errors. The timestamp helps you connect an error to a change you made or to the moment a feed dropped, so capture the wording and time before restarting if you can.
YouTube characterises red errors as critical and yellow errors as moderate. The important point is not the colour alone: read the actual error text and follow its suggested remedy. A critical error may prevent an event from starting or affect viewers; a moderate one may reduce quality. Do not treat a colour or a generic “starting” label as enough evidence to change bitrate, resolution, or keyframe settings.
If the error concerns an encoder starting, YouTube’s guidance for third-party encoders says to get a new stream key in Live Control Room and update the encoder. Do this only when it matches the situation, then ensure the replacement key is also the one configured for the Switchboard workflow. If the encoder signs in to YouTube directly without using a stream key, YouTube says to contact that software’s support team because an update may be needed.
If the health panel has no useful error but Switchboard reports “Receiving,” check the timing and event association again. You may be looking at a different event, or the destination may not have been started from the active workflow. If an error does appear, use it as the lead; do not repeatedly rotate keys or change unrelated video settings without evidence.
Apply a fix to the failing link
Match the action to the stage you have established. If no picture reaches Switchboard, correct the encoder’s output, URL, or key and test until the monitor shows incoming video. If the monitor is good but the destination is not live, verify the YouTube destination and event, then consult Live Control Room. If YouTube names an error, follow the relevant YouTube instruction and check whether the error clears.
| Evidence | Action to try | What to verify afterwards |
|---|---|---|
| Workflow remains “Not Receiving” | Check encoder output, workflow URL and key; inspect encoder errors and connection | Picture appears in the Confidence Monitor and workflow reports “Receiving” |
| Incoming picture is unstable or absent | Check the source, encoder output and connection; review encoder load and local output if available | Feed remains visible rather than appearing only briefly |
| Switchboard receives video, but YouTube does not start | Confirm the selected destination and event, then check Live Control Room | The correct event receives the feed and its status changes appropriately |
| YouTube reports a third-party encoder start error | Follow YouTube’s key-refresh guidance and update the encoder | The encoder uses the replacement key and the event health message changes |
| YouTube schedules rather than goes live | Check the title in the active template | The next attempt targets the intended titled event |
When the evidence points to the outbound connection, test that connection from the encoder’s location. YouTube advises contacting your internet service provider if the connectivity test identifies a problem. This is more useful than buying or replacing equipment without a confirmed hardware issue. The same applies to encoder load: use its own readings and output preview to establish a problem before changing the machine or switching platforms.
Make one relevant change at a time. After each, check the workflow and the YouTube event again. If several values change together, you may get a live picture without knowing which adjustment mattered, or make a second problem harder to diagnose. Keep a short note of the initial status, the change, and the result, especially if this channel must run overnight.
For a channel built around prerecorded material, fixing the start sequence does not resolve an eventual playback stop or a source that ends. Once the launch path is healthy, separate playback continuity from delivery; see how to fix a stream that stops when a rain video ends for that different failure mode.
Retest the full route
After a fix, test from the beginning of the route rather than relying on a single green indicator. Start the encoder, confirm that the intended picture reaches the Confidence Monitor, and wait for the workflow to show “Receiving.” Then start the YouTube destination and watch the matching event in Live Control Room for its health state and any new timestamped message.
Confirm that the public-facing event is the one you meant to start, and check it from a separate viewer session if appropriate. A healthy input monitor establishes that Switchboard has video; Live Control Room establishes what YouTube is reporting about the event. Neither should be used as a substitute for the other.
For an always-on channel, keep the workflow and event details somewhere available to the person on duty: which encoder output to start, which workflow is expected to receive it, and where the YouTube status is checked. Do not include the full stream key in a shared runbook. If a stream drops later, these notes let you identify whether it stopped at the same checkpoint or a different one.
If you need to avoid leaving a computer running simply to keep a file-based channel on air, StreamNeo removes that particular burden by taking an uploaded video and running it as a YouTube live stream while your computer is off. It is YouTube-only, so it does not replace the diagnostic checks for an existing Switchboard workflow or explain a destination error there.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why is my Switchboard stream stuck on starting?
There is no single established cause. Check whether video reaches the Switchboard Confidence Monitor, whether the workflow shows “Receiving,” and what the matching YouTube event reports in Live Control Room. Those checks locate the stage that needs attention.
Switchboard says “Receiving”, but YouTube is not live. What should I check?
Confirm the selected YouTube destination and that you are looking at its matching event. Then inspect the event’s Health Indicator and timestamped errors in Live Control Room; use the specific message to choose the next change.
Does a successful Confidence Monitor test make the stream live?
No. It confirms that video is reaching Switchboard from the encoder. You must still start and check the YouTube destination, and the YouTube event may have its own status or error.
Why is YouTube scheduling the stream instead of going live?
One documented Switchboard FAQ case is a missing title in the active template. Check and update that title if the symptom matches, but do not assume it explains a missing encoder feed or every delay.