You are here:
Platform Events Investigations
Surface high-volume platform event publishing and delivery patterns, runtime breakdowns, limit consumption breaches, and user and subscriber breakdowns in your org.
Considerations
- The Platform Events investigation works off platform telemetry already collected. It doesn't add a subscriber or count against your Platform Events quota or limits.
- No setup is required beyond enabling Scale Center.
To run a Platform Events investigation:
From Performance Analysis
- From Setup, in the Quick Find box, enter Scale Center, then click Performance Analysis.
- Click New Analysis.
- For type, select Platform Events.
- Select the time zone, start date, and end date.
- Give the investigation a name, then click Submit.
From the Org Performance Errors Chart
- From Setup, in the Quick Find box, enter Scale Center, then click Org Performance.
- In the Errors Chart, identify a spike of interest.
- Click the spike, then select Platform Events from the dropdown.
- Give the investigation a name, then click Submit.
| Category | Description |
|---|---|
| Key Takeaways | Summary of the most important findings across the investigation window, including limit headroom, publisher and subscriber bottlenecks, and recommended next steps. |
| Publishers | Runtime breakdown by publisher type (Apex and Flow), showing average run time, publish call duration, and which publishers contribute most to event volume. Most publisher duration comes from surrounding Apex execution, not the event bus itself. |
| Subscribers | Delivery performance by subscriber, including average delivery time and events per execution. Low events-per-execution ratios indicate a subscriber isn’t taking advantage of batching. |
| Limits | Hourly publish limit and rolling 24-hour delivery limit usage, expressed as a percentage of the org's allocation. Publish and delivery are separate allocations. Adding a subscriber to a topic increases delivery consumption without affecting publish usage. |
| Breakdown | Volume by user, integration, and topic. Identifies which users or integrations drive most publish activity and which topics consume the most delivery. Events published with no active subscribers are flagged as unnecessary limit consumption. |
| Runtime | Average publish and delivery run times over the investigation window, displayed as time-series charts. Delivery times consistently above 5 seconds per batch indicate subscriber logic that should be moved to asynchronous processing. |
