Streaming API Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Generic Streaming Allocations
| Description | Performance and Unlimited Editions | Enterprise Edition | Professional Edition | Free Orgs |
|---|---|---|---|---|
| Maximum streaming channels per org | 1,000 | 1,000 | 1,000 | 200 |
| Maximum number of concurrent clients (subscribers) across all channels and for all event types | 2,000 | 1,000 | 20 | 20 |
| Maximum number of delivered event notifications within a 24-hour period, shared by all CometD clients, with Durable Generic Streaming (API version 37.0 and later) | 1,000,000 | 200,000 | 100,000 | 10,000 |
| Maximum number of delivered event notifications within a 24-hour period, shared by all CometD clients, with generic streaming (API version 36.0 and earlier) | 100,000 | 100,000 | 100,000 | 10,000 |
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. Generic 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.