- Ably FAQs
- Account billing and packages
- Packages & Pricing
-
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
-
Reactor Queues, Events and Firehose
-
Migrating to Ably from an existing service
-
Connections
I've hit a max rate Token requests limit, what does this mean?
This means you've sent enough Token requests within the last second to surpass your limit or to be warned about your usage. Token requests are made by clients requesting tokens using signed token requests.
There are two types of token requests limit you can hit:
- tokenRequests.maxRate.warning - when you reach 50% of your quota.
- tokenRequests.maxRate.hard - when the hard limit on the account has been exceeded. Token requests will now be suppressed until the second is over.
If you need the ability to send more Token requests, we recommend you upgrade your account by increasing your monthly message quota from which Token request limits derive
How are instantaneous rate limits implemented?
An instantaneous rate limit is calculated based on the current rate of the operation per second. For example, a self-service package can publish at most 200 messages per second to their Ably Reactor queues; if you exceed this, messages above that point will be suppressed. This is done on a rolling probabilistic basis; for example, if you have a queue rule that attempts to publish 400 messages per second to a queue, each one will have a 50% chance of being rejected, with the suppression probability being continuously updated based on the current attempted publish rate.