--- schema_version: "1" id: b18fb6ee03bcb2c018c224bdf2a3e75fec573b76d58b5e54821440ccb909cccd title: Considerations for Event Processes collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_considerations_design_event.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_considerations_design_event.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 97b2b942a9e069659de016ad25f5089b065c52dcdfb0fff089280e72ebf9a3c4 description: These considerations are specific to processes that start when a platform event message is received. products: - Flow Builder - Salesforce Platform release: "264" --- # Considerations for Event Processes These considerations are specific to processes that start when a platform event message is received. ### Required Editions
Available in both Salesforce Classic and Lightning Experience
Available in: Performance, Unlimited, Enterprise, and Developer Editions
![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png) Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US). After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules."). ## Supported Platform Events Processes can subscribe to custom platform events and these standard platform events. - AIPredictionEvent - BatchApexErrorEvent - FlowExecutionErrorEvent - FOStatusChangedEvent - OrderSummaryCreatedEvent - OrderSumStatusChangedEvent - PlatformStatusAlertEvent ## Apex Actions You can’t use an event reference to set an sObject variable in the Apex class. ## Email Alerts Actions Email alerts can’t use values from platform event messages. For the process to send an email that contains values from the platform event message that starts the process, use this workaround. ## Flows Actions You can’t use an event reference to set a record variable in the flow, even when the platform event is specified as the record variable’s object. To pass values into the flow from the platform event message that starts the process, use this workaround. - In the flow, create a variable for each field in the platform event. Be sure to use compatible data types and make the variables available for input. - In the process, when you add the Flows action, use event references to assign each platform event field to its corresponding flow variable. ## Associating with a Record Use the process’s matching conditions to find exactly one record. If the process can’t find one record based on your matching conditions—because either it found multiple records or no records—the creator of the process receives an error email. If an error occurs, adjust the conditions in the process’s trigger to be more specific. ## Publishing Event Messages With event processes, we don’t block you from publishing the same event message that starts the process. To avoid creating an endless loop, make sure that the new event message’s field values don’t meet the filter criteria for the associated criteria node. If a platform event is configured to publish immediately, the process publishes each event message outside of the database transaction. If the transaction fails and is rolled back, the event message is still published and can’t be rolled back. So if you see an informational message under the selected platform event, consider whether you want the process to publish an event message only after the transaction commits successfully. ## Subscriptions Related List On the platform event’s detail page, the Subscriptions related list shows which entities are waiting to receive that platform event’s messages. The related list includes a link to each subscribed process. If flow interviews are waiting for that platform event's messages, one “Process” subscriber appears in the Subscriptions related list. ## Packaging When you package an event process, the associated object isn’t automatically included. Advise your subscribers to create the object or manually add the object to your package. For example, when you package an event process that’s associated with the Participants custom object, manually add the object to your package. ## Uninstalling Events Before you uninstall a package that includes a platform event, deactivate all processes that reference the platform event. ## Einstein Predictions A prediction event is sent for each Einstein prediction result, so use process matching conditions if you want your process to be triggered only by predictions on a specific object. For example, if your process acts only on predictions written to Lead records, add a matching condition to check that the Lead ID field equals the AI Predicted Object ID event reference. If your process updates a field that is used by an Einstein prediction, Einstein runs the prediction again and writes back the new results. The new results generate a new prediction event that could trigger your process again, resulting in a loop. To avoid creating a process loop, only update fields that aren’t used in Einstein predictions. #### See Also - [_Platform Events Developer Guide_: Decoupled Publishing and Subscription](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_considerations_decoupled_processes.htm) - [_Platform Events Developer Guide_: Platform Event Fields](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_define_ui.htm) - [_Platform Events Developer Guide_: Subscribe to Platform Event Messages with Processes](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_subscribe_process.htm)