Troubleshoot realtime connections and missing events

Trace a missing event through the app, channel, subscription and publication. A successful publish does not prove that a particular browser received the event.

Check the app key and region against the Realtime app you created. Verify network access from the affected device and inspect the client's connection state. Keep app secrets and Bird API keys on the server; the browser connects with the public app key.

Compare the setup with your first realtime event and connection lifecycle.

Inspect the request to your authorization endpoint. Confirm that the customer is signed in, the endpoint receives the intended socket and channel, and your authorization rule permits that exact subscription.

Do not resolve the error by making a customer channel public. Follow channel authorization and test a customer who should be denied as well as one who should be allowed.

Compare the app ID used by the publisher with the app key used by the subscriber. Check channel and event names character for character. Register the handler and wait for subscription success before publishing the test event.

Inspect the publishing call's result and server logs. A typo in the event binding can hide a message even when the channel subscription succeeded.

Refresh application state after reconnecting. Events sent during disconnection are not automatically replayed as a complete application history. The live order-status example shows a recovery pattern using your database.

Distinguish users from their individual connections. One person may have several tabs or devices. Read presence channels before treating connection changes as a person joining or leaving the application.

Realtime resources includes client, migration and operating guides.