Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

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 the long-running requests exceed the org default limit, all new Apex invocation requests are denied. 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	Type String Description The type of event. The value is always `ConcurrentLongRunningApexLimit`.
NUMBER_REQUESTS	Type Number Description Count of requests with an established Apex context executing for longer than 5 seconds in your org.
ORGANIZATION_ID	Type Id Description The 15-character ID of the organization. For example: `00D000000000123`.
REQUEST_ID	Type String Description The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID. For example: `3nWgxWbDKWWDIk0FKfF5DV`.
REQUEST_URI	Type String Description URI of the long-running Apex request that Salesforce terminated. Example /apex/ApexClassName
REQUESTS_LIMIT	Type Number Description Maximum count of requests with an established Apex context that can execute for longer than 5 seconds. When NUMBER_REQUESTS reaches this limit, then additional long-running Apex requests are terminated. (Asynchronous requests don’t count towards the limit.) See Apex Developer Guide: Lightning Platform Apex Limits. Example 10
TIMESTAMP	Type String Description The access time of Salesforce services in GMT. For example: `20130715233322.670`.
TIMESTAMP_DERIVED	Type DateTime Description The access time of Salesforce services in ISO8601-compatible format (`YYYY-MM-DDTHH:MM:SS.sssZ`). For example: `2015-07-27T11:32:59.555Z`. Timezone is GMT.
USER_ID	Type Id Description The 15-character ID of the user who’s using Salesforce services through the UI or the API. For example: `00530000009M943`

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).

Object Reference for the Salesforce Platform

Concurrent Long-Running Apex Limit Event Type

Fields

Usage

See Also