If resubs are missing from a Streamlabs Most Recent Subscriber file, open Stream Labels, select Most Recent Subscriber, tick include resubs, and save. That corrects the file’s setting; it does not recover a Twitch event Streamlabs never received or change what an on-stream widget displays.
Work out where the resub disappears before changing anything else. A text file, an event in Streamlabs, and an Event List or Alert Box on your broadcast are separate layers, with different settings and causes.
Enable resubs in the Most Recent Subscriber label
Open Stream Labels and go to Settings. In the label dropdown, select Most Recent Subscriber; this is the specific label that writes the latest subscriber information to a file. Tick include resubs. Streamlabs documents this as the setting to use when resubs are missing from the recent subscriber file in its support article on the missing-resubs issue.
The order matters. A checkbox for resubs in a different label, an alert, or a widget is not a substitute for enabling it on Most Recent Subscriber. Confirm the selected label name before saving. If you manage more than one Streamlabs profile or scene collection, also check that Stream Labels is using the profile you actually use for the affected broadcast.
This setting is about whether the label file includes resubs that Streamlabs has available to report. It is not an instruction to Twitch to send a notification, and it cannot create an event that did not arrive. Keep that distinction in mind as you troubleshoot: a correct file preference and a missing upstream event can produce the same visible symptom—no resub name in the file—but require different next steps.
Save the setting and verify the file
After ticking include resubs, use Stream Labels’ save control. Do not assume a changed checkbox has been saved simply because it remains visible while the settings window is open. Close or leave the settings only after saving, then check the actual file used by your streaming scene.
If you are not sure which file the scene reads, inspect the text-file path in the relevant Streamlabs label or source configuration. Compare that path with the file you open in your file browser. It is easy to adjust one file in Stream Labels while an OBS text source or another scene still points to a different copy. The displayed name or path should help you establish whether the two components are looking at the same file.
A controlled check is more useful than waiting for a real resub. After saving, look for the most recent value in the file and confirm that the scene’s text source reads that same path. Avoid editing the file by hand as a test: a manual change may show that the on-screen text source can read text, but it does not demonstrate that Stream Labels has received or written a resub event.
If a real resub has already occurred, compare the file’s contents with the available Streamlabs event history. Note what the file contains, whether it changes after a new event, and whether the expected event appears elsewhere in Streamlabs. This creates a useful boundary: if the event is absent from Streamlabs too, stop repeating file-setting changes and investigate event receipt instead.
For a channel that runs continuously, treat this as a configuration check rather than a reason to rebuild the broadcast. A label file can be tested independently of the video and audio loop. If you are also checking the broader operation of a nonstop channel, the article on keeping a YouTube livestream running after an SSH session closes covers a separate continuity problem; it will not change Streamlabs event handling.
Check whether the resub event reached Streamlabs
Open Streamlabs’ Recent Events or the relevant event feed and look for the resub there. If it appears in Recent Events but not in the Most Recent Subscriber file, revisit the label selection, the saved include resubs setting, and which file the scene reads. If it does not appear in Recent Events either, the label file cannot supply it. The problem is earlier in the chain.
Streamlabs says Twitch resub notifications may not be available when a subscriber does not share the resub in chat, because of API limitations. Its guidance on Twitch alerts and API limitations explains why a resub can be absent from the alert flow even though the person’s subscription has renewed. The subscriber’s choice not to post a chat message is not something you can correct by toggling a local label option.
That means the word “resub” can refer to two different things in practice: a subscription renewal on Twitch, and an event Streamlabs has received and can expose to a label or alert. Do not infer from an empty file alone that the subscription did not happen. Equally, do not infer that Streamlabs can display every renewal as a notification. Check the event feed and consider whether the resub was shared in chat before deciding which layer is at fault.
If other event types are also missing—not just resubs—check the Twitch connection. Streamlabs’ Recent Events connection troubleshooting guide recommends logging out of Streamlabs.com and Streamlabs programmes, disconnecting Streamlabs from Twitch’s Connections settings, clearing browser cookies and cache, and then signing in again to reconnect. Follow the current instructions on the support page, since account interfaces can change.
Reconnecting is a step for future event receipt, not a way to restore history. Streamlabs warns that past missing events will not be brought back by reconnecting. If the issue affects several event types, make a note of when you reconnected and test with an event that can be observed in the feed; do not treat the absence of an old event as proof that the connection still needs another reset.
Understand the chat-sharing and API limitation
For Twitch, the chat-sharing detail is important because it changes what you can reasonably expect to troubleshoot. Streamlabs’ documentation describes cases where a resub does not generate an alert or notification if the subscriber has not shared it in chat. In that case, there may be no corresponding event for Stream Labels, Recent Events, or a widget to display.
The file setting and the API limitation are not competing explanations for the same control. The setting tells the label whether to include resubs that are available to it. The API limitation concerns whether Streamlabs receives a notification in the first place. Enabling include resubs is still the right first check for a file-only problem, but it cannot force Twitch to provide an event that Streamlabs did not receive.
A sensible diagnostic sequence is therefore: first check the file setting and save it; then see whether the resub is in Recent Events; then assess whether chat sharing could explain a missing Twitch notification. If the event is not in the feed and other events are also absent, inspect the connection. If only an unshared resub is missing, repeatedly changing the file or widget is unlikely to help.
Keep the platform in view when using this guidance. The API limitation described here is about Twitch resub notifications; do not assume the same event semantics apply to another platform or transfer Twitch-specific steps to a different integration without checking that platform’s current documentation. Streamlabs’ own support pages are the best place to confirm whether their wording or interface has changed.
Inspect Event List or Alert Box event settings
A Stream Labels text file is not the same thing as an Event List widget or an Alert Box. The file supplies text for a source that reads it. Event List presents selected events in a widget, while Alert Box displays notifications according to its own platform and event settings. An event appearing in one does not prove that another is configured to show it.
If the resub is present in Recent Events but not on the broadcast, identify which display you mean. For an Event List, check the selected event types and the way the widget has been added to your streaming setup. Streamlabs’ Event List setup guide covers its configuration. For an alert, check the applicable platform and event settings, and use the alert test where available. Streamlabs’ Alert Box setup instructions describe that separate configuration.
Also check whether alerts are paused or otherwise disabled. A functioning event feed with no visible alert can be caused by display-side settings even when event receipt is working. The reverse is possible too: a configured widget cannot display a resub that never arrived. Keep the test focused on the component in question rather than changing label-file options to fix a widget.
| Where you can see the resub | Likely layer to check | What the result tells you |
|---|---|---|
| In Recent Events, but not in the text file | Stream Labels setting and file path | The event reached Streamlabs; check the selected label, saved option and file being read. |
| In Recent Events, but not in Event List | Event List selection and widget setup | The event feed works; check whether the widget is configured to include that event and is installed as intended. |
| In Recent Events, but not as an alert | Alert Box event settings, pause state and test | Investigate alert display behaviour separately from the label file. |
| In neither the feed nor the display | Event receipt, platform behaviour and connection | A display setting cannot recover an event missing upstream. |
The comparison is a guide, not a guarantee about what happened in an individual case. A test alert can confirm parts of the display path, but it does not necessarily reproduce the conditions of a real Twitch resub. Record exactly which test you ran and what it showed.
Check source visibility and display configuration
If the event is available but the broadcast still shows nothing, inspect the source in the scene that is actually live. In OBS or Streamlabs Desktop, confirm the browser source, text source, or widget source is present in the intended scene and not hidden behind another source. Check its visibility toggle, dimensions, and placement; a source outside the visible canvas can be active but unseen.
For a text label, verify the file path and refresh behaviour of the source, then check whether the file contains text at all. A blank file points back towards label output or event availability; visible text in the file but not on stream points towards the source path, visibility, or layout. A stale value may indicate that the scene reads another copy of the file or has not refreshed it, rather than a missing event.
For a browser-based widget, confirm that you are using the current widget source associated with the correct Streamlabs account and that the source is enabled in the live scene. Avoid sharing alert or widget URLs publicly; they can expose controls or identifiers that should remain private. If you need to replace a source after account reconnection, follow the current Streamlabs instructions and update the source in the broadcast software you actually use.
These checks are about visibility, not event ingestion. If the event is absent from Recent Events, making a source larger or moving it on the canvas will not make the resub arrive. If the event is in the feed and the test works, but the live scene remains blank, the display path becomes the stronger lead.
The same discipline helps with other continuous-stream issues: distinguish a display problem from the actual broadcast path. If you are building a pre-recorded loop rather than diagnosing alerts, the guide to running bhajans to YouTube Live in a loop with FFmpeg addresses the media loop itself, not Streamlabs subscriber events.
Retest and identify the failing layer
Retest one layer at a time and write down what you observe. Note whether the resub is visible in Recent Events, whether the file changes, whether the Event List includes it, and whether the Alert Box test appears. Include the platform, the Streamlabs surface you use, and the software version. This is more useful than saying simply that “resubs do not work”.
Use the results to choose the next action. If the event appears in Recent Events but the file omits it, recheck Most Recent Subscriber, include resubs, saving, and the file path. If it is in the feed but absent from a widget, follow the appropriate Event List or Alert Box setup. If it is absent from Recent Events, check the Twitch sharing/API limitation and whether other events are also affected before reconnecting.
If you contact support, provide the same evidence. Streamlabs’ support request process asks which software is being used, whether the notification appears in Recent Events, and whether a test notification works. Answering those points helps separate a receipt issue from a widget issue. Do not include a private stream key, password, or public alert URL in a support post.
For a channel that must stay on air, make changes at a time when you can observe the output and revert them if necessary. Alert and text overlays are separate from the video loop, so changing their configuration need not require rebuilding a stable stream. If you are reviewing other parts of a 24/7 setup, the article on choosing between a VPS and a cloud streaming service concerns continuity and operating choices, not Streamlabs event recovery.
The practical goal is not to make every layer agree by changing all settings at once. It is to find the first point where the expected event is missing. Once you know whether it is the file, the event feed, or the on-screen display, the next action is narrower and less likely to disrupt working parts of the broadcast.
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
How do I include resubs in the Streamlabs Most Recent Subscriber file?
In Stream Labels settings, select Most Recent Subscriber, tick include resubs, and save. Then verify the file that your scene reads; a different file path can make a correct setting appear not to work.
Does enabling the label setting bring back a missing Twitch resub?
No. The setting controls whether the label includes resubs that Streamlabs has received; it cannot recreate an event that never reached Streamlabs. Streamlabs notes that a Twitch resub may not produce a notification when the subscriber does not share it in chat, due to API limitations.
Why does the resub appear in Recent Events but not on stream?
That points towards the display layer rather than event receipt. Check whether you mean the text-file source, Event List, or Alert Box, then inspect its path or selected events, visibility, and test behaviour.
Will reconnecting Twitch restore old missing events?
Streamlabs says reconnecting can help with events going forward, but does not recover past missing events. If several event types are missing, follow the current connection troubleshooting steps and then test the feed rather than expecting historical events to reappear.