If Streamlabs’ Mini Feed is not showing new follows, tips, subscriptions or similar events, refresh the Twitch connection using Streamlabs’ recommended sequence. Sign out of Streamlabs apps first, disconnect Streamlabs from Twitch while signed out, clear your browser cookies and cache, then sign back in.
This process is intended to help events appear going forward; it will not restore events that are already missing. Follow the steps in order, and keep the Mini Feed separate from an alert that is merely not visible in your streaming scene.
Confirm which Mini Feed events are missing
First identify what you mean by “not showing”. Streamlabs’ Mini Feed, also called Recent Events, lists activity such as follows, tips and subscriptions. Note which types you expect to see and whether the feed is empty or only missing one kind of event. That description will help you tell whether the issue is with incoming events or with a particular alert’s appearance.
Check the feed itself in Streamlabs rather than relying only on what appears in your broadcast preview. An alert may be absent from a scene because of widget or scene configuration even when the Mini Feed has received the event. Conversely, an alert test can appear in a scene without establishing that the Mini Feed is receiving real events from Twitch.
If only one alert type is affected, write down that distinction before changing anything. For example, if follows appear but subscriptions do not, record that; if no new events appear at all, record that too. Avoid repeatedly changing alert layouts or sources before you have completed the specific connection refresh below. Streamlabs’ issue-specific guide recommends refreshing the Twitch connection, not guessing at a cause from the symptom alone.
The distinction matters if you use several tools. You may have Streamlabs.com open, Streamlabs Desktop running, Stream Labels open, and an alert widget loaded in another streaming application. The Mini Feed question is whether new event information reaches Streamlabs, while a widget question is whether a particular alert is displayed in the right place. Streamlabs’ guide to setting up Alerts describes how Alert Box can be used in Streamlabs Desktop, through the Streamlabs plugin for OBS, or as a browser source in other software; that display setup is distinct from this feed reconnection procedure.
Log out of Streamlabs apps and services
Before disconnecting anything in Twitch, sign out of Streamlabs.com and all Streamlabs software you are using. That can include Streamlabs Desktop and Stream Labels. The order is part of Streamlabs’ recommended fix: the relevant connection should be disconnected while you are logged out of Streamlabs.
Close or sign out of each application that is currently using the account, then sign out of the website. If you use only the website, signing out there is still required. If you use more than one Streamlabs application, do not assume that signing out of one has signed out of all the others.
This is a reset of the sign-in state, not a request to delete your account or remove your streaming scenes. You should not need to uninstall Streamlabs software for the documented sequence. Keep notes on any custom widget setup if it will help you check it later, but do not start replacing widget URLs yet unless the feed refresh makes that necessary.
Once logged out, leave Streamlabs signed out as you open Twitch’s connection settings. If an app signs you back in automatically, sign out again before proceeding. The aim is to follow the documented sequence cleanly, rather than to make unrelated changes while trying to work out what happened.
Disconnect Streamlabs in Twitch
While you remain logged out of Streamlabs, open Twitch’s Connections settings and find the Streamlabs connection. Streamlabs’ dedicated article identifies entries labelled “Streamlabs (Twitch Alerts)” or “Streamlabs / Streamlabs Dashboard”; the wording you see may depend on the entry. Disconnect the relevant Streamlabs connection there.
This step refreshes the authorisation between Twitch and Streamlabs. It is not the same as deleting a Twitch account, removing a channel, or changing a stream key. Check the name of the connection before removing it so you do not disconnect an unrelated service. For a reliable route to the setting, use Twitch’s own Connections page while signed into the Twitch account linked to the affected Streamlabs account.
Do not reconnect immediately from a Streamlabs app if you have not completed the next step. Streamlabs’ documented order is to disconnect while logged out, clear browser cookies and cache, and then log back into Streamlabs with the Twitch account. Keeping to that order makes the process easier to follow and avoids layering in extra changes that Streamlabs has not asked you to make for this issue.
If you manage multiple Twitch accounts, make sure the Twitch account open in the browser is the one used for the channel whose events are missing. If you are unsure, check the account identity before changing the connection. Do not infer that an event is missing because of a general Twitch or YouTube feed problem; this procedure is specifically about refreshing the Twitch-to-Streamlabs connection.
Clear browser cookies and cache
With Streamlabs still signed out, clear your browser’s cookies and cache. Streamlabs includes this step in its issue-specific instructions. Browser menus vary, so use your browser’s own privacy or history settings and choose the relevant stored site data and cached files. You do not need to clear data in unrelated apps as part of this particular sequence.
Be aware that clearing cookies can sign you out of websites and remove some saved session state. If your browser offers a choice of time range or site data, make a considered selection rather than clearing more than you intend. The important point in Streamlabs’ guidance is to clear browser cookies and cache before signing back into Streamlabs.
When that is done, close and reopen the browser if it helps ensure you are starting a fresh session. Do not treat clearing the browser as proof that the feed is fixed; it is one step in refreshing the connection. The next step is to sign back into Streamlabs using the Twitch account associated with the channel.
If you use more than one browser profile, make sure you clear the data in the profile you use for Streamlabs. Otherwise you may sign in again through a different profile with old session data still present. Keep the process simple: complete the sign-out, Twitch disconnect and browser clearing steps, then reconnect through Streamlabs.
Log back into Streamlabs
Return to Streamlabs.com and sign in with the Twitch account whose connection you just disconnected. If you use Streamlabs Desktop, Stream Labels or another Streamlabs app for the affected setup, sign into those as well. Streamlabs’ instructions describe reconnecting by logging back into the site and/or the relevant software using Twitch.
Read any account or authorisation prompt before accepting it, and check that the Twitch identity shown is the one you intend to use. If you have more than one channel or account, it is easy to reconnect the wrong one and then conclude that the refresh did not help. The point is to re-establish the same intended connection, not to switch accounts as a diagnostic shortcut.
After reconnecting, avoid changing several settings at once. First check whether new events appear in the Mini Feed. Streamlabs notes that widget or alert URLs may need updating after reconnection, but that is a follow-up for related alerts or widgets, not evidence that an event-feed problem is caused by a URL.
If your alert source in OBS or other streaming software stops behaving after the reconnect, compare its current browser-source URL with the one shown in your Streamlabs alert setup. Streamlabs’ alert setup instructions provide context for where an Alert Box can be added and tested. Updating a source URL may be necessary for that display path, but it should not be presented as a guaranteed fix for a Mini Feed that still receives no new events.
Check whether new events appear
Once you are signed back in, watch for a new, genuine event of a type you previously recorded as missing. The relevant question is whether new activity begins appearing from this point onwards. Do not expect the reconnect to backfill the period when the feed was empty: Streamlabs explicitly says that missing events will not be brought back and the change is for future events.
If new events appear, note the event type and time so you can distinguish the feed from a visual alert issue. Then check your broadcast scene separately if an alert still fails to show there. A Mini Feed entry and an on-screen alert are related parts of a creator’s setup, but success in one does not demonstrate success in the other.
If no new events appear, avoid repeating the connection sequence over and over without checking the account and symptom. Confirm that you signed into the intended Twitch account and that the Streamlabs connection was the one disconnected. Keep a short record of the steps completed, the affected event types, and whether any event appeared after reconnecting. Those details will be useful if you need Streamlabs support.
For creators who are also maintaining an always-on YouTube channel, separate account troubleshooting from broadcast continuity. A missing Streamlabs event does not by itself mean the live video has stopped. If the channel uses alerts to recognise viewer support, the practical background in how YouTube fan funding works can help distinguish YouTube’s viewer-support features from Streamlabs’ role in displaying notifications. If you are running a continuous channel from a computer, the trade-offs in running a continuous YouTube stream with a mini PC in India are a separate operating question, not a remedy for Mini Feed authorisation.
If alerts or widgets are also affected
Only move to broader alert troubleshooting if the symptom extends beyond the Mini Feed. Streamlabs’ general Alerts and Widget Troubleshooting guide covers checks for related alert and widget behaviour. It is broader than the issue-specific Mini Feed article, so treat its suggestions as follow-up checks for those symptoms, not as documented causes of an empty Mini Feed.
If an alert is not reaching a scene, check whether alerts are paused in Recent Events or whether Unlimited Alert Moderation Delay is holding alerts for approval. Then review the affected alert variation, any custom HTML or CSS, animation settings and widget theme. Make one change at a time and test the relevant alert so you can tell what changed. An alert test is useful for display troubleshooting but does not verify real event delivery to the Mini Feed.
If browser-based widgets remain troublesome, Streamlabs’ general guide also suggests refreshing browser sources, relinking the account, checking firewall or antivirus access and system date and time, clearing the streaming software’s browser cache, and resetting the API token. These are wider troubleshooting suggestions, not guaranteed fixes for the Mini Feed. A token reset can require updating widget URLs in the streaming software, so note the existing setup and follow Streamlabs’ instructions before changing it.
There are useful distinctions within that list. Browser-source refreshes and scene layering relate to what your audience sees; firewall, browser cache and account relinking are broader checks; a paused or moderated alert relates to whether an alert is being shown or held. Work on the check that matches the symptom rather than applying every item as if it were a single proven cause.
For a channel with a regular publishing routine, it can help to keep feed checks alongside other operational notes, without conflating them. A planned playlist rotation, for example, is covered in how to schedule different playlists in OBS with Advanced Scene Switcher; it is not part of the Streamlabs connection fix. This is useful precisely because it keeps event troubleshooting, visual alert checks and stream scheduling as separate jobs.
Escalate if the feed remains empty
If the documented sequence is complete and new events still do not appear, contact Streamlabs support with a concise account of what you observed. Include the Twitch account or channel context, which Mini Feed event types are absent, whether the feed is entirely empty, which Streamlabs apps you use, and the order in which you signed out, disconnected, cleared browser data and signed back in. Do not send passwords, stream keys or other secret credentials.
State clearly whether the issue affects only the Mini Feed or also affects alerts in your streaming scene. If alerts are involved, say whether a dashboard test appears and whether a real event appears in Recent Events; those observations describe different paths. Include the time of a recent test or genuine event if available, but do not claim that a test proves the live event connection is healthy.
Streamlabs’ dedicated support article is the best reference for the specific reconnection order, while its broader troubleshooting checklist applies when alert or widget symptoms accompany the feed issue. Keep those scopes separate when describing the problem. You can also check Streamlabs’ current official guidance before making further account or token changes, since interface labels and support instructions can change.
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 this bring back events that disappeared earlier?
No. Streamlabs says reconnecting is intended to help new events appear going forward, not to restore events already missing from the feeds. Record any gap you need to report, but do not expect a backfill from the connection refresh.
Should I disconnect Streamlabs in Twitch before or after logging out?
Log out of Streamlabs.com and all Streamlabs software you are using first. While still logged out, disconnect the relevant Streamlabs entry in Twitch Connections, clear browser cookies and cache, and then sign back into Streamlabs with the intended Twitch account.
What if the Mini Feed works but my alert is not visible on stream?
That points to a display or widget symptom rather than necessarily to missing Mini Feed events. Check the alert source, its URL and relevant widget or scene settings using Streamlabs’ broader alert guidance; a test alert does not prove that real events are reaching the Mini Feed.
Is this a YouTube feed problem?
The documented fix is for the connection between Twitch and Streamlabs, not a YouTube feed issue. Keep the account connection and any separate broadcast or scene problem distinct when you troubleshoot.