View an Event’s Subscribers on the Platform Event’s Detail Page

1. From Setup, enter Platform Events in the Quick Find box, then select Platform Events.
2. Click your event’s name.

   On the event’s definition page, the Subscriptions related list shows all the active triggers and processes that are subscribed to the platform event.

3. To get more details about a subscriber, click the subscriber name in the Subscriptions related list. For a trigger, details include its implementation and API version. For a process, details include its version number and API name.

   Why are you seeing flow version details when you click a process? Similar to a flow, a running instance of a process is a flow interview. The information that you see on the Flow Version page is about the process. You can click the flow API name of the process to view the list of processes for your org.

   Note

The list shows the replay ID of the event that the system last processed (Last Processed Id field) and the event last published (Last Published Id field). Knowing which replay ID was last processed is useful when there is a gap in the events published and processed. For example, if a trigger contains complex logic that causes a delay in processing large batches of incoming events.

Also, the Subscriptions list shows the state of each subscribed trigger. Trigger states can be one of the following.

• Running—The subscriber is actively listening to events.
• Idle—The subscriber hasn't received events for some time and is not actively listening to events. When new events are sent, the trigger receives the new events after a short delay and switches to the Running state.
• Error—The subscriber has been disconnected and stopped receiving published events. A trigger reaches this state when it exceeds the number of maximum retries with the EventBus.RetryableException. Trigger assertion failures and unhandled exceptions don’t cause the Error state. To resume trigger execution, fix the trigger code and save it. For a managed package trigger, redeploy the package after fixing the trigger. To resume a process, deactivate it and then reactivate it.
• Suspended—The subscriber is disconnected and can’t receive events due to an internal error. To resume trigger execution, try saving the trigger again. For a managed package trigger, redeploy the package. To resume a process, deactivate it and then reactivate it.