First establish where the repeated video appears: in the stream preview or archive, or only in one person’s player. Those are different problems, and the evidence will tell you whether to inspect the outgoing video source or that viewer’s playback.
“Store promo loop” does not identify a particular YouTube feature, shop platform, encoder or production app. There is no basis for assuming YouTube has a documented bug by that name, or that an undocumented reset will fix it. Start with what you can observe, then narrow down the setup before changing it.
Is the repeat in the broadcast or just your playback?
Ask three questions before touching settings: does the repeat appear in Live Control Room, is it present in the completed live archive, and can another viewer see it? Write down what each person actually observed, including roughly when the repeated segment began. A viewer saying “the promo is looping” is useful, but it does not yet tell you whether the source feed is repeating or their player is replaying content.
If the repeating segment is visible in the creator’s Live Control Room preview, the signal YouTube is receiving may already contain that segment. That points your first checks towards the active media, scene, playlist or output in the software that sends the stream. It is a troubleshooting inference from the documented encoder workflow, not a YouTube diagnosis of a “store promo loop”.
If the completed archive repeats the same promo as well, that is further evidence that the repeated material was present in the recorded broadcast. It still does not identify the cause: an intended playlist, a stuck media source, an incorrect scene, or another part of the production chain could all warrant checking. Compare the times and visible transitions rather than guessing from the title or thumbnail.
If the preview and archive look normal but one viewer reports repetition, focus first on that viewer’s player, device and viewing context. Check whether other viewers can reproduce the same behaviour before changing the live output. A single report is not proof that the channel itself is sending a repeated video.
A practical first note might be: “Preview: normal at 14:05; archive: normal around the reported time; viewer A on a phone reports the promo returning; viewer B on a laptop does not.” That gives you a testable difference. Avoid changing several settings at once, because doing so makes it harder to know which observation changed.
Compare the Live Control Room preview and archive
YouTube’s encoder workflow has you send a stream using a server URL and stream key, then check its preview in Live Control Room before going live. The YouTube Help guide to creating a live stream with an encoder describes that workflow and says streams under 12 hours are automatically archived. The archive can therefore be a useful comparison when one is available, though it is not a real-time diagnostic and may not answer every playback question.
During a live event, note what the preview shows when the promo is expected to change. If it shows the same clip beginning again, capture the time and inspect the source that should have taken over. If the preview shows the expected content but a viewer reports a repeat, ask them to refresh their observation with the time, device and player context, rather than immediately restarting the stream.
After the event, compare the archive at the reported timestamp. Look for the same opening frame, a repeated transition, or a return to the promo after the intended next item. Distinguish an actual repeat from a viewer rewinding or resuming at an earlier position. YouTube’s live stream settings documentation describes DVR controls, which can let viewers pause, rewind and continue during a live stream. That means two viewers may not be looking at the same moment in the programme.
If your event is scheduled, confirm that you are checking the intended stream in Live Control Room, not a previous event or a different scheduled entry. YouTube documents scheduled stream management in its encoder workflow, but the names and layout you see can vary as the product changes. Use the actual stream and event details on screen rather than relying on an old bookmark or remembered sequence of clicks.
You do not need to stop the stream merely because someone reports a repeat. First check whether the outgoing preview also shows it, and whether the report is reproducible. If the stream is live and the promo is harmful or misleading, make a considered decision about switching to a known-good scene using your normal production process; do not experiment with undocumented resets while on air.
Check the playlist and active video source
If the preview or archive contains the repeat, inspect the playlist or media source that feeds the programme. Start by asking what was supposed to play immediately before and after the promo. Check whether that next item is present, enabled and assigned to the active sequence or scene. A missing item, a playlist that contains the same file twice, or a source that is still active after a transition are all possibilities to verify, not assumptions to treat as fact.
Look at the order and identity of the files, not only their displayed names. Two files may have similar titles or thumbnails. If your software shows a file path or source label, compare it with the intended promo and next item. Do not rename or move files in the middle of a live session unless you understand how that software resolves media references; a change that breaks the source can replace repetition with a blank or frozen picture.
If you run a deliberate rotation, compare the actual schedule with the expected one. A playlist designed to show one promo between longer programme blocks may appear repetitive if its rotation rules are misunderstood, even though the output is following its configured order. For planning a rotation rather than diagnosing an active fault, the guide to rotating playlists on a 24/7 YouTube channel covers the separate scheduling problem.
Check whether the source itself is configured to loop. Looping may be intentional for a single ambience file or a short holding screen, but it may not be appropriate for a promo that should yield to other material. Make a note of the current setting before changing it, and test the change on a non-public or otherwise controlled run if your setup allows. Do not assume a YouTube player loop control changes the playlist inside your encoder.
For a file-based programme, test the intended sequence with a short, recognisable set of clips before returning to the full schedule. A visible title card or spoken slate can make transitions easier to identify. Keep the test narrow: confirm whether item A advances to item B, and whether the promo returns at the point the schedule expects. Guidance on looping multiple video files in FFmpeg for YouTube Live is relevant if FFmpeg is actually part of your setup; it is not a fix to apply to unrelated software.
Review the encoder or playout app settings
When the repeat is in the outgoing preview, identify the programme path that supplies it. You might use an encoder, a scene-based production app, a hardware appliance, a store platform’s own live feature, or a cloud playout tool. The word “store” could refer to several things, so do not follow instructions for a guessed product. Record the exact app or device name and version if visible, then inspect its active scene, source and playlist using that product’s documented controls.
In a scene-based app, confirm which scene is actually live and which media source is visible in it. A source can continue playing behind another scene, or the live scene can differ from the one you expected to select. Check whether the promo is set to restart when a scene becomes active, whether a transition returns to it, and whether a hotkey or automation rule changes scenes. These are questions to ask of your own configuration; their labels and behaviour differ by product.
In a command-line or scripted setup, read the current command or job definition before editing it. Confirm the input files, sequence, repeat option and destination stream key without publishing the key in screenshots or support messages. If you need a controlled comparison, a simple test pattern can establish whether the stream output is advancing independently of the promo media; the FFmpeg test-pattern walkthrough is useful only for an FFmpeg workflow.
Compare the output in your production app with the preview in Live Control Room. If the app’s programme monitor already shows the promo repeating, focus on that app or its inputs. If the app monitor advances correctly but YouTube’s preview differs, preserve the timestamps and capture both views; you have a useful boundary for support to investigate. The streaming ingestion overview may help you map how a feed reaches YouTube without treating the transport as the cause by default.
YouTube’s live streaming tips recommend testing ahead and monitoring stream quality. That is sound practice, but it is not a specific cure for repeated promos. For an always-on channel, use a planned maintenance window to test a changed playlist or source, and retain the last known-good configuration so that you can revert if the output worsens.
Test with another viewer and device
When the creator’s preview and available archive do not show the repeat, test from a second account or ask another person to view the same live stream. Ideally compare two different devices or browsers, and note whether each viewer is signed in, using an app or browser, and viewing live or a replay. The point is not to collect a crowd of reports; it is to see whether the symptom follows one playback context or appears consistently.
Ask the first viewer to report the exact time and what they did immediately beforehand. They may have paused, scrubbed backwards, reopened a tab or resumed playback. Those actions can make the stream appear to revisit material without the outgoing channel repeating it. Be neutral: the viewer’s observation matters, but the playback path must be checked before attributing it to the broadcast.
YouTube documents repeating a video or playlist in its loop videos or playlists help page. Treat that as a relevant check when the problem is confined to a viewer’s playback and the control is available in their context. The page does not establish that one repeat toggle controls every type of live-stream repetition, so do not claim that turning it off must resolve the symptom.
Have the viewer check the player’s repeat controls where available, and then watch a fresh portion without seeking backwards. If the issue persists, compare the same live moment on another device. A setting or playback state may differ between contexts, and an app update or browser change can alter what controls are shown. Do not ask viewers to clear data or reinstall an app as a first response when you have not established that the issue is local to them.
Keep a controlled test for the next run
Once you have a likely source, change one thing at a time. If the playlist contains a duplicated promo, correct that entry and test the transition. If a viewer’s player was repeating, have them check the available repeat control and observe a fresh segment. If the source remains unclear, reproduce the sequence with a short test programme before applying a broader change to an always-on schedule.
A test is more useful when it has a clear expected result. For example: “At the end of the promo, the stream should show the station slate, then the next scheduled clip.” Record whether that happened in the production app, Live Control Room and a second viewer’s player. If those points disagree, preserve the discrepancy rather than adjusting unrelated settings to make the screens look similar.
Do not buy a capture card, encoder or other hardware on the strength of this symptom alone. The official guidance cited here explains streaming and playback workflows; it does not identify a physical product that fixes a repeating video. Hardware may be appropriate for a different, established need, but first establish where the repeat enters the path.
For an always-on channel where keeping a computer running is itself the operational burden, StreamNeo can remove that particular task: upload the video, provide the YouTube stream key, and the broadcast can continue with your computer switched off. It does not identify why a particular source repeats, and you should still check the file and channel setup before changing how you run it.
What evidence to collect before escalating
If the checks do not isolate the cause, collect enough detail for the store platform, production software or YouTube support route to understand the path. Include the store or service name, the exact streaming app or device, how the video reaches YouTube, and whether the output is a file playlist, live camera feed or another source. If you do not know one of those details, say so rather than filling in a guess.
Provide the date and time with timezone for the report, the live stream URL or event identifier, and timestamps where the repeat begins and ends. Say whether those times came from the live preview, archive or a viewer’s player. A short screen recording or screenshots can help if they show the relevant app and transition, but remove stream keys, account details and other sensitive information before sharing.
Summarise the results in a small comparison:
| Check | What to record | What it helps distinguish |
|---|---|---|
| Live Control Room preview | Whether the promo repeats and the time observed | What was visible in the incoming live preview |
| Completed archive | Whether the same segment repeats at the matching time | Whether the recorded broadcast contains the repetition |
| Production app or device | Active scene, media source and expected next item | Whether the source or programme sequence needs checking |
| Second viewer | Device, app or browser, and whether the symptom recurs | Whether the report is confined to one playback context |
Include what you already tested and the result of each change. “Restarted everything” is difficult to investigate; “the preview showed clip B, while viewer A saw clip A again at 14:05” is actionable. Do not send a stream key in a support ticket or public forum. YouTube’s encoder instructions explain that the key is part of the connection workflow, so treat it as a credential rather than ordinary diagnostic text.
Escalate to the service responsible for the part that differs. If the production app monitor already repeats, provide its vendor with the source and schedule details. If the outgoing preview and archive are correct but one playback context is not, report the viewer steps and device. If the preview in Live Control Room differs from the production app, share the time-aligned evidence with the relevant support route rather than asking for a generic reset.
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 does my YouTube Live keep playing the same video?
First compare the Live Control Room preview and, when available, the archive with what the viewer sees. If the repeat is present in the outgoing preview, inspect the active source, scene and playlist; if only one viewer sees it, investigate that playback context. The phrase “store promo loop” does not identify a documented YouTube fault.
Should I restart the stream or reset YouTube Studio?
Not as a first step. A restart can interrupt viewers and may erase useful evidence without fixing a repeated media source or local playback state. Identify where the repetition appears, record the time, and use the documented controls for the software or device you have actually identified.
Does turning off loop fix a live stream?
A viewer-side repeat control is worth checking when the issue appears only for one viewer and the relevant control is available. YouTube’s loop guidance covers repeating videos or playlists, but it does not establish that the same setting controls every kind of live-stream repetition. Compare with another viewer and the broadcast preview before drawing a conclusion.
What should I tell support if I do not know what “store” means?
Give the exact name of the shop or streaming service you use, the production app or device, and how the video is sent to YouTube. Include whether the repeat is in the preview, archive or one viewer’s player, with the time and test results. Those details are more useful than guessing at a product or requesting an undocumented reset.