Operational Error Codes

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

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

Database is initializing connection.

The number of connected clients has reached its limit.

Database had connection issues and connection was not able to be established.

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 trying to authorize the WebSocket connection.

Verify user information on connect.

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 starting the Postgres CDC extension which is used for Postgres Changes.

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

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

Connection against Tenant database is still starting.

JWT exp claim value it's incorrect.

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

JWT signature was not able to be validated.

Token received does not comply with the JWT format.

Check to see if we require to run migrations fails.

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

Error when creating partitions for realtime.messages.

Error when pooling the replication slot.

Error when preparing the replication slot.

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.

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.

Maximum number of WAL senders reached in tenant database.

Learn more:

• Configuring max WAL senders

The replication slot is being used by another transaction.

Error on RLS policy used for authorization.

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

Error when trying to delete a subscription for postgres changes.

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

The table you are trying to listen to has spaces in its name which we are unable to support.

Change the table name to not have spaces in it.

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 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 create a counter to track rate limits for a tenant.

Error when trying to decrement a counter to track rate limits for a tenant.

Error when trying to delete subscriptions that are no longer being used.

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 trying to find a counter to track rate limits for a tenant.

Error when trying to increment a counter to track rate limits for a tenant.

Unable to LISTEN for notifications against the Tenant Database.

Payload sent in NOTIFY operation was JSON parsable.

Error when setting up Authorization Policies.

Error when trying to subscribe to Postgres changes.

Error when handling track presence for this socket.

Error when trying to update a counter to track rate limits for a tenant.

Unauthorized access to Realtime channel.

Unhandled message received by a Realtime process.

An unknown data type was processed by the Realtime system.

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

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

Presence event type not recognized by service.

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