Problem
Paid-message leaderboard shows stale data after a browser-source refresh failure.
Solution
Root Cause / Diagnostic:
Leaderboard overlays rely on persistent REST polling or long-lived WebSocket connections that can silently drop without visible errors. When local cache fails to invalidate or API limits throttle calls, the graphic freezes on outdated session totals.
Actionable Fix:
1. Configure Automatic Cache Invalidation: In the OBS browser source URL, append a dynamic query string parameter (e.g., ?nocache=1) and check "Shutdown source when not visible" in source properties.
2. Implement an API Polling Fallback Script: Ensure the custom leaderboard script utilizes a watchdog timer that re-initializes socket handshakes if no payload is received within 180 seconds.
3. Set Up Control Deck Refresh Hotkey: Map a single button on your macro deck to cycle the browser source visibility off/on to force an instant render refresh.
Pro Tip:
Test your leaderboard by pushing a $0 test transaction from your dashboard 5 minutes before air; if the graphic does not register the test within 2 seconds, execute an immediate cache flush before going live.
Leaderboard overlays rely on persistent REST polling or long-lived WebSocket connections that can silently drop without visible errors. When local cache fails to invalidate or API limits throttle calls, the graphic freezes on outdated session totals.
Actionable Fix:
1. Configure Automatic Cache Invalidation: In the OBS browser source URL, append a dynamic query string parameter (e.g., ?nocache=1) and check "Shutdown source when not visible" in source properties.
2. Implement an API Polling Fallback Script: Ensure the custom leaderboard script utilizes a watchdog timer that re-initializes socket handshakes if no payload is received within 180 seconds.
3. Set Up Control Deck Refresh Hotkey: Map a single button on your macro deck to cycle the browser source visibility off/on to force an instant render refresh.
Pro Tip:
Test your leaderboard by pushing a $0 test transaction from your dashboard 5 minutes before air; if the graphic does not register the test within 2 seconds, execute an immediate cache flush before going live.