- Ably FAQs
- Ably error codes
- Client errors
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Integrations
-
Migrating to Ably from an existing service
Error code: 42910 - Rate limit exceeded; request rejected
This error indicates you have hit a hard limit on your account, and the request you made has been rejected. The limit will only remain in effect until the period to which it applies has passed. For example, if the limit is an instantaneous rate limit, then typically the limit will last for a maximum for six seconds, after which and you will be able to continue to publish messages.
The error message will typically indicate what limit you have hit. For example, take the following error message.
Rate limit exceeded; request rejected (nonfatal);
metric = channel.maxRate;
interval = 2018-01-05:10:10:3;
permitted rate = 5000;
current rate = 5015;
scope = channel:[YOUR APP ID]:[YOUR CHANNEL]
(status: 429, code: 42910) (code: 42910, http status: 429)
The metric in this example is channel.maxRate, which represents max rate of messages allowed to be published on a channel per second.
You can find out more about all limits that exist for your account.
To ensure Ably can provide continuity of service for all customers under all conditions, every account has a hard upper limit in regards to usage, either based on monthly, hourly or per second limits. Find out more about why we have hourly or per second rate limits on all accounts.