You are here:
OM Standard: Considerations about PlatformEvents Mode
PlatformEvents mode improves performance in OM orchestration. When deciding whether to run PlatformEvents mode, there are a few things to consider, such as Salesforce allowances for certain methods or events.
Whether you decide to switch to PlatformEvents mode or not, you can change your mind whenever you want. For instructions on doing so, see Order Management Standard: Set Up Platform Events
Salesforce Allowances
Salesforce allows a certain number of platform events and asynchronous Apex method executions, which are both used by Order Management. For more details about those allowances, see this Salesforce Platform Developer Guide's page: Platform Event Allocations
These allowances are shared by all the modules that are in the org, not just Order Management.
-
Platform event publication: 250,000 per hour.*
-
Asynchronous Apex method executions**: 250,000 per day, or 200 X the number of user licenses in your org, whichever is greater.
* You can ignore any limits on platform event delivery.
** Asynchronous Apex methods include things such as batch Apex, future methods, Queueable Apex, and scheduled Apex methods.
Going over the allowance for platform events: If your entire org (OM along with all other modules in the org), uses more platform events than allowed by Salesforce, then any new events will pause for an hour. At that time, the allowance resets, and those events are processed.
Going over the allowance for asynchronous Apex method executions: If your entire org, meaning OM along with any other module, executes more asynchronous Apex methods than allowed by Salesforce in a 24-hour period, then any new events will pause for 24 hours. At that time, the allowance resets, and those events are processed.
Your Expectations from Order Management
Given the allowance of platform events and Asynchronous Apex executions, it's important to understand when Order Management generates them.
Order Management generates one platform event and one Asynchronous Apex method for each callout or autotask that fires in an orchestration plan.
For example, let's say that an order's orchestration plan contains 7 callouts, 5 autotasks, and a number of push events and manual tasks.
We can ignore everything except the callouts and autotasks. Add them together to get 12, so that's 12 platform events and 12 Asynchronous Apex method executions.
If a callout fails and is retried, then that's TWO platform events and TWO Asynchronous Apex method executions: one for each attempt.
