SignalR Troubleshooting Basics

Start with the symptom

Real-time issues may look like missing notifications, stale status, delayed updates, or reconnect loops. Capture what the user expected to update and what actually happened.

Check connection behavior

Browser devtools can show whether real-time connections are opening, closing, reconnecting, or failing. Network conditions and proxies can affect these connections.

Compare environments

Test another browser, network, account, and environment if available. This helps determine whether the issue is local, account-specific, or system-wide.

Document timing

For real-time bugs, timestamps matter. Include when the event happened, when the UI updated, and whether refresh changed the state.