Fix Test alert dispatch so OBS/browser-source overlays receive the alert #111

New issue

Closed

opened 2026-07-06 20:11:11 -05:00 by Gitchegumi · 0 comments

Gitchegumi commented

2026-07-06 20:11:11 -05:00

(Migrated from github.com)

Problem

Clicking Test alert in the Alerts editor does not send the alert to the browser source / overlay runtime.

The editor has a Copy OBS URL control and a Test alert button, so the expected workflow is clear: copy the OBS browser-source URL, add/open it in OBS or a browser, then click Test alert from the dashboard and see the alert fire in that browser source.

Right now, the test alert does not reach the browser-source overlay.

Observed on the Alerts editor page:

Route: /dashboard/gitchegumi-gaming/alerts
App version shown in the UI: v0.10.4
Layout selected: Tips / 1920 x 1080
User clicks Test alert
Browser source does not receive/show the test alert.

Expected behavior

When Test alert is clicked, the app should publish a synthetic alert event through the same runtime delivery path used for real Ko-fi/Twitch/YouTube events.

The OBS/browser-source overlay should receive and render the test alert without requiring a real external event.

Actual behavior

The alert test appears to be local to the editor, incomplete, or not being published to the overlay subscription/channel used by the browser source.

Acceptance criteria

Browser source opened from Copy OBS URL receives the alert when Test alert is clicked.
Test alert is scoped to the current workspace/channel/layout and does not broadcast to unrelated overlays.
Test alert uses representative sample data for the selected alert type.
Browser source does not require an authenticated dashboard session to receive/render the alert.
Delivery uses the same event pipeline/channel semantics as real incoming events where practical.
Failure states are visible in the UI or logs if dispatch fails.

Areas to verify

The test-alert API/action publishes to the same queue/socket/realtime channel that overlay clients subscribe to.
The overlay URL includes enough workspace/layout/alert identifiers to subscribe to the correct room.
The editor and browser-source runtime agree on channelSlug, workspace ID, layout ID, and alert type names.
Auth/CORS/session behavior does not block unauthenticated OBS browser-source clients.
NPM/proxy/websocket settings are not required for local editor testing beyond the app's documented deployment configuration.

## Problem Clicking `Test alert` in the Alerts editor does not send the alert to the browser source / overlay runtime. The editor has a `Copy OBS URL` control and a `Test alert` button, so the expected workflow is clear: copy the OBS browser-source URL, add/open it in OBS or a browser, then click `Test alert` from the dashboard and see the alert fire in that browser source. Right now, the test alert does not reach the browser-source overlay. Observed on the Alerts editor page: - Route: `/dashboard/gitchegumi-gaming/alerts` - App version shown in the UI: `v0.10.4` - Layout selected: `Tips` / `1920 x 1080` - User clicks `Test alert` - Browser source does not receive/show the test alert. ## Expected behavior When `Test alert` is clicked, the app should publish a synthetic alert event through the same runtime delivery path used for real Ko-fi/Twitch/YouTube events. The OBS/browser-source overlay should receive and render the test alert without requiring a real external event. ## Actual behavior The alert test appears to be local to the editor, incomplete, or not being published to the overlay subscription/channel used by the browser source. ## Acceptance criteria - [ ] Browser source opened from `Copy OBS URL` receives the alert when `Test alert` is clicked. - [ ] Test alert is scoped to the current workspace/channel/layout and does not broadcast to unrelated overlays. - [ ] Test alert uses representative sample data for the selected alert type. - [ ] Browser source does not require an authenticated dashboard session to receive/render the alert. - [ ] Delivery uses the same event pipeline/channel semantics as real incoming events where practical. - [ ] Failure states are visible in the UI or logs if dispatch fails. ## Areas to verify - The test-alert API/action publishes to the same queue/socket/realtime channel that overlay clients subscribe to. - The overlay URL includes enough workspace/layout/alert identifiers to subscribe to the correct room. - The editor and browser-source runtime agree on `channelSlug`, workspace ID, layout ID, and alert type names. - Auth/CORS/session behavior does not block unauthenticated OBS browser-source clients. - NPM/proxy/websocket settings are not required for local editor testing beyond the app's documented deployment configuration.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gitchegumi/GitchAlerts#111

No description provided.

Rows
Columns