Operational Error Codes

The number of channels you can create has reached its limit.

The channel was shut down and an error system message was pushed to the client.

Error when fetching the publication tables (OIDs) during the periodic check; the existing OIDs, replication slot and subscribers are left untouched.

The rate of joins per second from your clients has reached the channel limits.

A single client sent Presence updates too frequently and had its channel closed. This usually means Presence is being used for high-frequency updates it is not designed for.

Learn more:

• Troubleshooting guide for the ClientPresenceRateLimitReached error

Reserve Presence for slow-changing state and use Broadcast for high-frequency updates such as live cursors, or throttle your track() calls.

The number of connected clients has reached its limit.

The rate of attempts to connect to the database has reached the limit.

Realtime was not able to connect to the tenant's database due to not having enough available connections.

Learn more:

• Connection management guide

Verify your database connection limits.

Error when dropping the replication slot after the publication became empty; the poller stops so the temporary slot is released with the connection.

Error when trying to connect to the WebSocket server.

Verify user information on connect.

Error executing a database transaction in tenant database.

Error when calling another realtime node.

Error when running a query against the tenant database.

Error when starting the Postgres CDC extension which is used for Postgres Changes.

Phoenix converted an exception into a 4xx HTTP response (for example a request to an unknown route). The log includes the underlying error and status.

Phoenix converted an unhandled exception into a 5xx HTTP response. The log includes the underlying error and status to explain a server error that request metrics alone would not surface.

The number of connections you have set for Realtime are not enough to handle your current use case.

The subscription connection pool hit too many database timeouts and should be increased.

Connection against Tenant database is still starting.

The payload provided to Realtime on connect is invalid.

The JWT provided on connect is expired or is missing required claims (`role` and `exp`).

Payload from track event sent to Presence isn't a map.

Scheduled task for realtime.message cleanup was unable to run.

The rate of joins per second from your clients has reached the limit and the connection was refused.

JWT signature was not able to be validated.

Failed to generate a JWT signer — check your JWT secret or JWKS configuration.

Token received does not comply with the JWT format.

Received a WebSocket message that is empty, invalid JSON, or missing required fields (`ref`, `topic`, or `event`). The connection is kept alive but the message is dropped.

The rate of messages per second from your clients has reached the channel limits.

The cached `migrations_ran` count did not match the tenant database and is being reconciled.

Failed to reconcile the `migrations_ran` count mismatch between the cache and the tenant database.

Error when running the migrations against the Tenant database that are required by Realtime.

No API key was provided in the `x-api-key` header or `apikey` query parameter.

Realtime was unable to find the expected messages partition.

Error when creating partitions for realtime.messages.

Error when pooling the replication slot.

Error when preparing the replication slot.

Limit of presence events reached globally.

The connection was rejected because this project only allows private channels.

A database query was canceled, usually due to a statement timeout.

The configuration provided to Realtime on connect will not be able to provide you any Postgres Changes.

Verify your configuration on channel startup as you might not have your tables properly registered.

Realtime has been disabled for the tenant.

Learn more:

• Troubleshooting guide for suspended projects

Your project may have been suspended for exceeding usage quotas. Contact support with your project reference ID and a description of your Realtime use case.

Realtime is a distributed application and this means that one the system is unable to communicate with one of the distributed nodes.

Realtime is currently restarting.

Postgres changes still waiting to be subscribed.

The replication connection was terminated and a recovery window has been opened.

The database check failed while trying to recover the replication connection.

Replication connection timed out during initialization.

Maximum number of WAL senders reached in tenant database.

Learn more:

• Configuring max WAL senders

Error when the replication poller process fails to connect to the database on startup.

The replication poller gave up after the maximum number of consecutive retries and stopped the tenant's Postgres Changes workers.

The replication connection recovery window was exceeded and the connection was terminated.

The replication slot is being used by another transaction.

The periodic replication slot lag check could not be completed, typically because the tenant database connection was unavailable. The check is skipped and retried on the next watchdog interval.

The replication slot WAL lag has exceeded 50% of `max_slot_wal_keep_size`. The replication connection is shut down and will be restarted to prevent the slot from being invalidated by PostgreSQL.

Error on RLS policy used for authorization.

Error returned when calling another realtime node over RPC.

Error when starting the replication and listening of errors for database broadcasting.

Error when trying to clean up all subscriptions on subscription manager initialization or OID change.

Error when trying to delete a subscription for postgres changes.

Error when the subscription manager process fails to connect to the database on startup.

Our framework to syncronize processes has failed to properly startup a connection to the database.

The tenant you are trying to connect to does not exist.

Verify the tenant name you are trying to connect to exists in the realtime.tenants table.

RPC request within the Realtime server has timed out.

You are trying to use Realtime without a topic name set.

Error when trying to checkout a connection from the tenant pool.

Error when trying to broadcast database changes (realtime.messages) to subscribers.

Error when trying to check the processes on a remote node.

Unable to connect to Project database.

Realtime was not able to connect to the tenant's database.

Error when trying to delete a tenant.

An error were we are not handling correctly the response to be sent to the end user.

Error when handling a broadcast message.

Error when handling a presence message on a channel.

An error while replaying messages.

Error when setting up Authorization Policies.

Error when trying to subscribe to Postgres changes.

Error when handling track presence for this socket.

Unauthorized access to Realtime channel.

An unexpected message was received by the replication connection process.

Unhandled message received by a Realtime process.

An unhandled error occurred.

An error we are not handling correctly was triggered on a channel.

An error we are not handling correctly was triggered on a controller.

An unexpected error occurred while processing an incoming WebSocket message. The connection is kept alive but the message is dropped.

Presence event type not recognized by service.

Received a HTTP request with a body that was not able to be processed by the endpoint.

Warning when `realtime.send` or `realtime.send_binary` cannot insert the message.

Learn more:

• Realtime troubleshooting guide