Troubleshooting realtime

#The connection closes with 4401, 4408 or 1013

• Cause: 4401: the ticket was bad, expired or reused, or the user signed out. 4408: a rule or limit refused the connection or a message (size, events per second). 1013: the client didn't read fast enough.
• Check: The close code in your onStatus/onError handler; the channel's rules; Realtime › Settings for limits.
• Fix: Let the SDK fetch a new ticket; allow SUBSCRIBE for the channel; keep messages small; handle messages faster (Channels and connections).
• Verify: The status reaches live and stays there.

#Published messages don't arrive

• Cause: The publisher isn't allowed to PUBLISH, the channel names differ, or the receiver connected after the message was sent.
• Check: The publish call's response (a refusal is an error there) and the exact channel names on both sides.
• Fix: Allow PUBLISH for the sender; after reconnecting, catch up with replay from the last stream_seq you saw.
• Verify: Both sides see the same messages, in order.

#Database change events don't arrive

• Cause: Change capture isn't on for that table, the write went through a direct Postgres connection, the statement changed no rows, or the listener may not subscribe to db.table.<table>.
• Check: Realtime › Database change data capture; how the write was made.
• Fix: Turn capture on for the table and allow SUBSCRIBE on its channel (Database change events).
• Verify: Insert a row through the API; an event with row_count: 1 arrives.

#Presence shows people who left, or one person several times

• Cause: A connection that vanished without closing stays listed for about 90 seconds; each tab or device is its own connection.
• Check: How many tabs or devices the person has open.
• Fix: Close connections when a page is left (channel.close()); group presence by user id in your app (Presence).
• Verify: After closing a tab, it disappears from presence at once.

#Still stuck?

Email outreach@sovaria.in with your project URL, the time it happened (with time zone), the X-Request-ID response header or the trace_id from the error body, and the channel name and the close code. Never send keys, passwords, tokens or your users' data.