Loading

Salesforce Platform: Suspend and Resume Platform Event Subscriptions

Udgivelsesdato: Mar 31, 2026
Beskrivelse
  1. Platform Events:

    • Salesforce's event-driven messaging architecture for real-time integrations.
    • Enables apps to communicate inside and outside Salesforce by sending and receiving event messages (notifications).
    • Ideal for asynchronous messaging, event-driven integrations, and notifications.
    • Example use cases: Notify external systems when a case is escalated or send order updates to a fulfillment system.
  2. Event Subscriptions:

    • Listeners that process Platform Events via triggers, flows, or external systems.
    • Subscribers can carry out actions based on the event messages they receive.
  3. Scenario:

    • During system maintenance or troubleshooting integration issues, you may need to temporarily pause event processing without deleting the subscription configuration. This ensures that the setup remains intact while addressing the issue.

Users may find the need to modify Platform Event Triggers, using PlatformEventTriggerConfig.  Per documentation:

"If a trigger is running and subscribed to a platform event, new configuration settings take effect after you suspend and resume the trigger. You can suspend and resume a trigger from the platform event detail page by clicking Manage next to the Apex trigger in the Subscriptions related list. For more information, see View and Manage an Event’s Subscribers on the Platform Event’s Detail Page."

The only way to directly suspend or resume a Platform Event Subscription is via the User Interface.  There is no current functionality to suspend and resume subscriptions programmatically.

 

 

Løsning

Manage Platform Event Subscriptions through the User Interface on the Subscriptions related list for a platform event.

It is possible to delete and recreate the trigger by deactivating Apex programmatically, which will delete the Platform Event Subscription and create a new subscription after the affected automation is set back to active, as a workaround.

Vidensartikelnummer

002186624

 
Indlæser
Salesforce Help | Article