Newer Version Available
Concurrent Long-Running Apex Limit Event Type
Concurrent Long-Running Apex Limit events contain information about
long-running concurrent Apex requests in your org that Salesforce terminated after reaching
your org’s concurrency limit. Requests with an established Apex context that execute for 5
seconds are counted towards your org’s limit of concurrent long-running requests.
(Asynchronous requests don’t count towards the limit.) When there are more than 10
long-running requests (org default limit), additional long-running requests are
terminated. This event type is available in the EventLogFile object in API version
45.0 and later.
For details about event monitoring, see the Trailhead Event Monitoring module or REST API Developer’s Guide.
Fields
| Field | Details |
|---|---|
| EVENT_TYPE | |
| NUMBER_REQUESTS |
|
| ORGANIZATION_ID | |
| REQUEST_ID | |
| REQUEST_URI |
|
| REQUESTS_LIMIT |
|
| TIMESTAMP | |
| TIMESTAMP_DERIVED |
|
| USER_ID |
Usage
For example, you can monitor Concurrent Long-Running Apex Limit log counts to get a benchmark or plot a count by hour. To identify where the limit was exceeded, see the REQUEST_URI field. Then, cross-reference this data with Apex Execution event data where the average RUN_TIME exceeds 5 seconds. To identify synchronous requests only, cross-reference event data with the QUIDDITY field in Apex Execution event data. For example, QUIDDITY NOT IN (A,BA,F,Q,S) and CALLOUT_TIME (>5000).