If Streamlabs Recent Events or the Mini Feed has stopped showing new Twitch follows, subscriptions, tips or other events, refresh the Streamlabs–Twitch connection using Streamlabs’ prescribed sequence. Log out, disconnect Streamlabs from Twitch, clear browser cookies and cache, then sign back in with Twitch.
That sequence is intended to help new events appear going forward; it is not a way to restore events that have already gone missing. If the event feed updates but an Event List or alert is still absent from your stream, troubleshoot that widget separately and check whether its URL needs updating after reconnecting.
Check which events are missing
Start by identifying where the problem appears. Recent Events, also called the Mini Feed in some Streamlabs interfaces, is the event feed you see in Streamlabs. An Event List is a visual widget you can show to viewers, while an Alert Box displays alerts on the stream. They are related to stream events, but they are not the same display.
Open Streamlabs and compare the feed with the stream preview. Are new events missing from the Streamlabs feed itself, or are they present in the feed but not visible on the broadcast? If they are absent from Recent Events or the Mini Feed, use the account reconnection sequence below. If they appear in the feed but not in the preview, the account may be connected correctly and the widget or broadcasting software may be the part to check.
Note whether the issue affects every event type or only one. Write down what you expect to see, such as a follow or a shared Twitch resubscription, and when you first noticed the gap. This is a practical way to separate a broad connection problem from an event-specific behaviour. Avoid assuming that one missing event means the whole account connection is broken.
For a channel with a long-running broadcast, the distinction matters: an overlay can stop rendering while the stream itself continues. The checks for showing recent events on a YouTube livestream concern a different platform and a viewer-facing display, but the general distinction between an event feed and an on-stream list is useful. This procedure here is specifically for Twitch; do not apply its platform steps as a fix for another service.
Before changing anything, make a note of the widgets and alerts you use and which broadcasting program contains them. You do not need to remove sources or rebuild an overlay just to begin the account fix. A brief record makes it easier to spot whether an URL or source needs attention afterward.
Log out of Streamlabs
The first step in Streamlabs’ dedicated guidance is to sign out of Streamlabs.com and of any Streamlabs software currently in use. That can include Streamlabs Desktop or Stream Labels. If you are signed in on more than one Streamlabs product, log out of each one before changing the Twitch connection.
This order is important because the next step is to disconnect Streamlabs from Twitch while you are logged out of Streamlabs. Leaving a Streamlabs session open in a browser or desktop application can make it less clear whether the old authorisation is still active. Close or sign out of those sessions first rather than jumping straight to a browser-source refresh.
You can follow Streamlabs’ Recent Events / Mini Feed troubleshooting instructions as the reference for this sequence. The account names and menu labels can change, so use the current official instructions if your screen differs. Do not treat a missing historical item as evidence that logging out did not work; the stated aim is future events.
Disconnect the Streamlabs connection from Twitch
While still logged out of Streamlabs, open Twitch’s connected-app settings and disconnect the Streamlabs entry used for alerts or the Streamlabs dashboard. Make sure you are working in the Twitch account whose events are missing. If you manage more than one channel, disconnecting an authorisation on the wrong account will not refresh the connection for the affected channel.
The action removes the existing authorisation between Twitch and Streamlabs. It is not the same as deleting your Twitch account or removing your broadcast from the channel. If the Twitch page asks you to confirm the disconnection, verify that the named app is Streamlabs before proceeding. Twitch’s official connected applications settings are the place to review authorised connections; if Twitch changes its settings layout, consult its current Help pages rather than relying on an old screenshot.
Do not sign back into Streamlabs yet. The prescribed order continues with clearing browser data, then signing in with Twitch so Streamlabs can establish a fresh connection. Reconnecting in a different order may leave uncertainty about whether the old browser session or authorisation was reused.
If a team member or another browser profile also accesses the same Streamlabs account, ask them not to change the connection during this short process. You want one deliberate disconnect and a clean sign-in, not several simultaneous account changes that make it hard to tell what succeeded.
Clear browser cookies and cache
With Streamlabs still logged out and its Twitch connection disconnected, clear your browser’s cookies and cached data. Streamlabs’ dedicated sequence calls for clearing both. Use the browser settings for the profile you used to access Streamlabs, not a different browser profile that has no saved Streamlabs session.
Cookies can retain sign-in state, while cached files can leave an older interface or session data in the browser. Clearing them is part of resetting the browser side of the connection; it is not a repair for data already missing from the feed. Browser menus differ, so consult the current help for your browser if you are unsure how to clear the relevant data. You may be signed out of other sites in that browser as a result, depending on the options you select.
If you are concerned about losing useful browser sessions, first check the browser’s choices for which data to remove and select the cookies and cached files requested for this procedure. Do not clear unrelated saved passwords or other data unless you intend to. After clearing the data, close and reopen the browser if its own guidance recommends doing so, then move to the sign-in step.
This is a browser account-connection remedy, not an instruction to clear the cache inside your streaming software. If the Streamlabs feed starts updating but a browser-source widget remains blank in OBS or another program, that is a separate symptom with a separate checklist.
Sign back in with Twitch
Now sign in to Streamlabs.com and any Streamlabs software you use with the Twitch account connected to the channel. Choose the Twitch sign-in or connection option so Streamlabs can request a new authorisation. Follow Twitch’s authorisation prompt and confirm the account shown is the one you intend to use.
Once signed in, check Recent Events or the Mini Feed for a new event when one is available. Do not use an old missing entry as the test: Streamlabs warns that the reconnect will not bring back events already missing from the feeds, and is intended to help moving forward. The official Streamlabs article states that limitation directly.
A practical check is to wait for a real new event that should be recorded, then see whether it appears in the feed. If you are using an available test function for a visual alert, remember that a test alert checks display behaviour and does not necessarily prove that a real Twitch event has been recorded in Recent Events. Keep the two checks separate.
If new events still do not appear, revisit the sequence in order: every Streamlabs session logged out, the correct Streamlabs connection removed from the correct Twitch account, browser cookies and cache cleared, and sign-in completed with Twitch. Avoid repeatedly disconnecting accounts without checking which account is authorised; that can create more uncertainty without addressing the original symptom.
For a channel whose broadcast is part of a broader always-on workflow, account health is only one piece of reliability. Keep a record of the feed symptom separately from any streaming interruptions, as explained in this 24/7 music streaming workflow. The account reconnect procedure does not restart a broadcast or guarantee that an event will appear.
Check widgets and alert URLs
After reconnecting, check whether you use a Streamlabs Event List or Alert Box on the stream. Streamlabs describes the Event List as a widget for displaying recent events; it can be used in Streamlabs Desktop, its OBS plugin, or compatible broadcasting software as a browser source. The viewer-facing widget can have a problem even when the dashboard feed is working.
Streamlabs warns that widget or alert URLs in broadcasting software may need to be updated after the reconnect. If you use OBS or another program, compare the source URL with the current URL in the relevant Streamlabs widget settings. Do not assume that copying an old URL forward is sufficient. Streamlabs’ alert setup instructions explain its widget workflow; use the current product instructions to locate the URL for your widget.
If the URL is current but the display is still missing or stale, Streamlabs’ broader widget troubleshooting recommends checking whether alerts are paused, refreshing or re-adding the browser source, relinking the account where appropriate, clearing the streaming software’s browser cache and running a test alert. These checks apply to an on-stream alert or widget symptom; they are not substitutes for the Recent Events account sequence above.
Also check the source’s visibility and placement in your scene. A browser source can load but be covered by another source, positioned outside the canvas, or configured in a way that makes its content hard to see. If you use custom HTML or CSS, a theme, alert variations or moderation delay, review those settings only when relevant to the display or event behaviour. Change one thing at a time so you can tell whether the correction helped.
Streamlabs’ widget troubleshooting guide is the primary reference for those display checks. The distinction is useful if you also maintain a 24/7 scene: guides such as setting OBS output resolution separately from the base canvas deal with broadcast configuration, whereas a stale Event List URL is a widget configuration issue.
Interpret event-specific gaps carefully
If the reconnection helps most events but one kind remains absent, check whether Streamlabs documents a platform-specific condition for that event. Its troubleshooting material notes that some Twitch resubscriptions may not appear unless the subscriber shares the resubscription in chat. That is a specific behaviour, not an explanation for a generally empty feed.
The same material discusses delayed YouTube subscriber alerts, but that note is not a Twitch fix and should not be used to diagnose this article’s Twitch-only procedure. Platform behaviours differ, and a setting or delay documented for one service should not be transferred to another. Check Streamlabs’ current official guidance for the platform and event type you actually use.
If you can identify a particular event that should have appeared, note the event type and whether the relevant Twitch action was visible elsewhere. Then compare with current Streamlabs and Twitch documentation. This gives support teams a more useful description than “the feed is broken” and avoids changing the whole overlay for a single event type.
For a practical channel checklist, keep the account connection, feed, and visible overlay as separate items. The golden rules for a successful YouTube live stream are aimed at a different platform, but the habit of checking each part of a broadcast workflow independently can help you avoid confusing an account symptom with a viewer-facing display problem.
Decide what to do next
Use the location of the symptom to choose the next action. If Recent Events or the Mini Feed itself is not receiving new Twitch events, use the account sequence in order and then watch for a new event. If the feed is updating but the viewers cannot see the Event List or alert, inspect the widget URL and browser source instead.
| What you observe | First check | What the check can tell you |
|---|---|---|
| New Twitch events are absent from Recent Events and the Mini Feed | Complete the Streamlabs logout, Twitch disconnect, browser-data clear and Twitch sign-in sequence | Whether a refreshed account connection helps new events appear |
| Events appear in the feed but not on the stream | Check the Event List or Alert Box, its URL, source state and scene visibility | Whether the issue is the on-stream widget rather than the feed |
| Most events appear, but one type does not | Check current platform-specific guidance for that event type | Whether a documented event condition may apply |
| An old event is still missing after reconnecting | Do not treat it as a failed reconnect; the process is for future events | The sequence is not a historical recovery method |
If the correct account was used and the sequence has been completed but new events remain absent, consult Streamlabs support with the event type, approximate time and steps already tried. If the only failure is a viewer-facing widget, include the broadcasting software and whether refreshing or replacing its source changed the display. Do not send passwords or stream keys in a support request.
If you are also planning a separate always-on YouTube channel, keep its software and platform choices distinct from this Twitch repair. This article’s steps are for Streamlabs’ Twitch connection; a setup such as an Indian classical music YouTube stream with OBS addresses a different broadcasting workflow, not a way to restore Twitch history.
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
Will reconnecting Streamlabs restore events already missing from the feed?
No. Streamlabs says this reconnect sequence is intended to help events appear moving forward and will not bring back events already missing from the feeds. Check for a new event after reconnecting rather than using an old gap as the test.
Do I need to update my alert or widget URL afterward?
Possibly. Streamlabs warns that widget or alert URLs in broadcasting software may need updating after the reconnection, so compare the source URL in your streaming software with the current URL in the Streamlabs widget settings.
What if the feed updates but the event list is not visible on stream?
Treat that as a widget or display issue rather than a Recent Events feed issue. Check that alerts are not paused, refresh or re-add the browser source, verify the URL and scene visibility, and run a test alert if appropriate.
Does this procedure apply to platforms other than Twitch?
No. The account-disconnection and sign-in sequence described here is for refreshing the Streamlabs–Twitch connection. For another platform, check Streamlabs’ current official guidance for that platform rather than assuming the Twitch steps apply.