Konduit puts alerts on stream through a Browser Source in OBS. When alerts don't reach your stream, work through these checks in order. Each one rules out a different cause.
1. Check the Browser Source is open
- In Konduit, open Overlays and look at the status at the top of the OBS Browser Source panel.
- Ready · waiting for OBS means no Konduit source is open in OBS. Add one: see Put Konduit's overlays in OBS.
- Live with a count means OBS has that many Konduit sources open. Go to the next check.
- Unavailable means the local source did not start. Quit and reopen Konduit.
OBS has to run on the same computer as Konduit, and you have to be signed in to Konduit. If a row shows Not available right now, sign in first.
2. Send a test
Choose Send test next to Standard (or Test on the separate source you use).
- Browser Source test sent. and the test shows in OBS: the source works. Go to check 4.
- Open the source in OBS before sending a test.: OBS has no Konduit source open. Add it, then test again.
- Konduit says the test was sent but nothing shows in OBS: right-click the Browser Source in OBS and choose "Refresh". If Konduit told you a port was busy and the source moved, choose Copy URL again and paste the new address into your Browser Source in OBS.
3. Check the overlay switches
On Overlays, each overlay card (Alert Overlay, Chat Overlay, Sub Overlay) has a switch in its corner. If the card reads Hidden, that overlay does not show in OBS and its sound is off. Turn the switch back on so it reads Active.
If you use separate sources, check that the Browser Source in OBS is the size the overlay card shows under Width and Height, and that it is not hidden or covered in your OBS scene.
4. Check the alert queue
- Open the Konduit tray menu (the Konduit icon in your menu bar, or in the taskbar tray on Windows). If Pause queue is ticked, alerts wait in the queue. Click it again to let them play.
- On Alerts & TTS, a low Max alerts per minute holds alerts back during busy moments.
5. Check what each alert is allowed to do
- On Integrations, each card has an On-stream alerts switch. When it is off, the card says Alerts are off. Events are still received, counted and logged. Turn it on for the platform or service that should alert.
- On Alerts & TTS, Dismiss Thresholds hide alerts below an amount you set (the money is still counted). Set a threshold to 0 to turn it off.
6. Events that arrived while Konduit was closed
Tips and merch orders reach Konduit's server first, and the app collects them from there. If the app collects one more than 10 minutes after the server received it (for example, one that came in while Konduit was closed), it is counted in your revenue and listed in Event Logs, but it doesn't fire an alert. On the free plan, tips and orders the server received before your account's first check on this computer are counted silently the same way. That is on purpose, so opening Konduit never floods your stream with old alerts.
Sound but no picture, or picture but no sound
- No sound anywhere: check the lane's Volume on Alerts & TTS is not at 0 (Muted). See Alert sounds and volume.
- While a Browser Source is open, alert sounds play from that source, so they reach your stream through OBS. Check the source's audio in OBS's audio mixer.
- Text-to-speech always plays from the Konduit app, not from the Browser Source.
Still not working
Open Settings → Debug & Logs and choose Send debug logs.... Konduit saves your recent logs as a zip in your Downloads folder. Email it to support@konduit.gg with what you tried.