Keep it running

Fix missing donations and silent OBS alerts

Check source connections, pending membership prices, OBS audio and support diagnostics step by step.

Checked against Subathon v4.2.2 · 2026-09-12

An event is missing#

Check Nguồn for the selected provider and connection status. Check Live history for a pending review. Check Membership for an unpriced tier. Then check whether Recent Events is enabled and whether “real events only” excludes the entry. Provider events without enough trustworthy fields may be held for review or ignored; do not infer success from a green connection alone.

An OBS alert is missing#

Open the output URL from the OBS page in a browser. Check the notification’s global switch, profile switch and event-type switch. Run a preview and check the queue. If the browser receives it but OBS does not, verify the Browser Source URL, source visibility and scene. If neither receives it, send diagnostics.

The local page cannot connect#

Check that Subathon.exe is still running. Read the actual address in its window: the port may be different when another app uses the default. Open that exact address and update OBS URLs if necessary. If a previous instance is still open, close it normally and launch once.

Send a useful report#

Use Gửi log in the app’s support dialog. A manual report includes recent donor names, donation messages/amounts, source payloads, rules, queue and diagnostic context, subject to size limits. Credentials and private source URLs are redacted. Check whether it says sent or saved locally; a local copy is in data/support-reports. Keep the report ID. After the on-screen countdown, you can send another report from the same tab. Old app versions are not excluded just because a newer version exists.

What we can verify#

These guides were checked against the stable 4.2.2 ZIP, isolated local browser operation, and the matching source regression tests. Live paid donations, Google account authorization, every OBS audio setup and AI performance on other PCs were not re-tested in this audit. Provider test alerts may differ from real payments. This documentation excludes experimental features.

Still stuck?

Keep your report ID and tell us which step behaves differently.

Get help