PushTopic Streaming Allocations
These default allocations apply to consumers of PushTopic Streaming in all API versions.
| Description | Performance and Unlimited Editions | Enterprise Edition | All other supported editions |
|---|---|---|---|
| Maximum number of topics (PushTopic records) per org | 100 | 50 | 40 |
| Maximum number of concurrent clients (subscribers) across all channels and for all event types | 2,000 | 1,000 | 20 |
| Maximum number of delivered event notifications within a 24-hour period, shared by all CometD clients | 1,000,000 | 200,000 | 50,000 (10,000 for free orgs) |
| Socket timeout during connection (CometD session) | 110 seconds | 110 seconds | 110 seconds |
| Timeout to reconnect after successful connection (keepalive) | 40 seconds | 40 seconds | 40 seconds |
Maximum length of the SOQL query in the Query field of a PushTopic record | 1,300 characters | 1,300 characters | 1,300 characters |
| Maximum length for a PushTopic name | 25 characters | 25 characters | 25 characters |
For free orgs, the maximum number of events within a 24-hour period is 10,000. Free orgs include Developer Edition orgs and trial orgs (all editions), such as partner test and demo orgs created through the Environment Hub. Sandboxes get the same allocations as their associated production orgs.
Note
If you exceed the default event delivery allocation, you receive this error: 403::Organization total events daily limit exceeded. The error is returned in the Bayeux /meta/connect channel when a CometD subscriber first connects or in an existing subscriber connection. For more information, see Streaming API Error Codes. PushTopic event notifications that are generated after exceeding the allocation are stored in the event bus. You can retrieve stored event messages as long as they are within the retention window of 24 hours.
If you have scenarios that warrant an increase in the number of delivered event notifications within a 24-hour period, contact Salesforce.
See Also
j