Platform Event Allocations

Common Platform Event Allocations

The following allocations apply to standard-volume and high-volume platform events.

High-Volume Platform Event Default Allocations

If your org has no add-on licenses, default allocations apply for event publishing and delivery that can't be exceeded. The default allocation is enforced daily to ensure fair sharing of resources in the multitenant environment and to protect the service. The publishing allocation is how many events you can publish using any method, including Apex, APIs, flows, and processes. The delivery allocation is how many event notifications can be delivered to CometD subscribers, including the empApi Lightning component. It excludes non-CometD subscribers, such as Apex triggers, flows, and processes. The publishing allocation is higher than the delivery allocation because there can be various types of subscribers. Published event messages that are delivered to non-CometD subscribers, such as Apex triggers, flows, and processes, don’t count against the delivery allocation.

The number of delivered events to CometD clients is counted per subscribed client. If you have multiple client subscribers, your usage is added across all subscribers. For example, you have an Unlimited Edition org with a default allocation of 50,000 events in a 24-hour period. Within a few hours, 20,000 event messages are delivered to two subscribed clients. So you consumed 40,000 events and are still entitled to 10,000 events within the 24-hour period.

If you exceed the default event delivery allocation, you receive an error. For more information, see Streaming API Error Codes in the Streaming API Developer Guide. Event messages 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 72 hours.

High-Volume Platform Event Add-On License and Usage-Based Entitlement

If your org has the add-on license, your allocation for delivered events to CometD clients moves to a monthly entitlement model. The add-on increases the 24-hour allocation of delivered event notifications by 100,000 per day (3 million a month) as a usage-based entitlement. The entitlement gives you flexibility in how you use your allocations. The entitlement isn’t as strictly enforced as the default allocation. With the entitlement, you can exceed your 24-hour event delivery allocation by a certain amount. The entitlement is reset every month after your contract start date. Entitlement usage is computed only for production orgs. It isn't available in sandbox or trial orgs. For more information, see Usage-based Entitlement Fields.

Salesforce monitors event overages based on a calendar month, starting with your contract start date. If you exceed the monthly entitlement, Salesforce contacts you to discuss your event usage needs. The entitlement used for monitoring monthly event overages is the daily allocation multiplied by 30.

When you purchase an add-on license, the hourly event publishing allocation increases by 25,000 events per hour.

The maximum event message size that you can publish is 1 MB. If your event object has hundreds of custom fields or many long text area fields, you could hit this limit. In this case, the publishing call gets an error.

Monitor Your High-Volume Event Usage Against Your Allocations

Determine how to check event usage for your org.

For more information about the limit usage values that the limits REST resource returns, see Limits and List Organization Limits in the REST API Developer Guide.

Monitor 24-Hour and Daily Event Usage with PlatformEventUsageMetric

To get usage data for event publishing and CometD-client delivery, query the PlatformEventUsageMetric object. The usage metrics stored in PlatformEventUsageMetric are separate from the REST API limits values. The REST API limits resource returns the maximum and remaining allocations for platform events and change data capture events. PlatformEventUsageMetric contains actual event usage data broken down by type of event for platform events and change data capture events.

PlatformEventUsageMetric usage data is available for the last 24 hours, ending at the last hour, and for historical daily usage for the last 45 days. Use PlatformEventUsageMetric to get visibility into your usage trends.

For more information, see Monitor Platform Event Publishing and Delivery Usage.

Monitor Hourly Event Delivery Usage with REST API

To monitor your org's event delivery hourly usage, make a REST API call to the limits resource every hour. The difference between the results obtained in the last 2 hours shows how many events were delivered in the last hour.

For example, you make a call at 12:00 PM and see that you have 40,000 events remaining. Then you run the same call at 1:00 PM and see that you have 38,500 events remaining. The returned responses indicate that 1,500 events were delivered to your CometD subscribers between 12:00 PM and 1:00 PM.

These results are examples of the responses that a GET request to the /services/data/v47.0/limits URI returns.

1First call result:
2{
3...  
4"MonthlyPlatformEvents" : {
5    "Max" : 50000,
6    "Remaining" : 40000
7  },
8
9...
10}
11 
12Second call result:
13{
14...  
15"MonthlyPlatformEvents" : {
16    "Max" : 50000,
17    "Remaining" : 38500
18  },
19
20...
21}

Standard-Volume Platform Event Allocations

The following allocations are for standard-volume events defined in API version 44.0 and earlier.

If you exceed the event delivery allocation, you receive an error. For more information, see Streaming API Error Codes in the Streaming API Developer Guide. Standard-volume event messages that are generated after exceeding the allocation are stored in the event bus. You can retrieve stored standard-volume event messages as long as they are within the retention window of 24 hours.

To monitor your standard-volume event delivery usage, use the limits REST API resource, and inspect the DailyStandardVolumePlatformEvents value. And to monitor the publishing usage, inspect the HourlyPublishedStandardVolumePlatformEvents value. For more information, see List Organization Limits in the REST API Developer Guide.

¹To request a higher number of standard-volume events delivered to CometD clients, contact Salesforce to purchase an add-on license. The add-on license increases your daily limit of delivered events by 100,000 more events. For example, for Unlimited Edition, the add-on license increases the daily limit of delivered events from 50,000 to 150,000 events. You can purchase multiple add-ons to meet your event requirements for CometD clients. To avoid deployment problems and degradation in service, we recommend that the number of events delivered to CometD clients not exceed 5 million per day. If you require more external events, contact your Salesforce representative to understand how the product can scale to meet your needs.