--- schema_version: "1" id: 548ecefa0bc79c0e5a3b7b4d14b13f08fe0dbbd4ecc56bbe897c47571a740098 title: Concurrent Long-Running Apex Limit Event Type collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_eventlogfile_concurrentlongrunningapexlimit.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_concurrentlongrunningapexlimit.htm source_site: developer.salesforce.com content_type: documentation content_hash: bae43c01d90a560b6cc8dc5ef60cb73594340bab640f09d7cec7ba8589326ac7 description: 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. --- # 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](https://trailhead.salesforce.com/en/modules/event_monitoring/units/event_monitoring_intro "HTML (New Window)") or [REST API Developer’s Guide](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_rest.meta/api_rest/using_resources_event_log_files.htm "HTML (New Window)"). ## 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](https://developer.salesforce.com/docs/atlas.en-us.264.0.apexcode.meta/apexcode/apex_gov_limits.htm#in_topic_non_transactional_gov_limits_section). 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](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_apexexecution.htm "Apex Execution events contain details about Apex classes that are used.") 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). #### See Also - [EventLogFile Supported Event Types](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_supportedeventtypes.htm "The EventType field in the EventLogFile object supports these events. Some common fields, such as CPU_TIME and RUN_TIME, can have null or zero values depending on how the events are generated for a given feature. Sometimes, three quotation marks appear around event data containing special characters in the CSV file. The third quotation mark is necessary for tools and applications to parse the field data at the correct field value boundary.") - [EventLogFile](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile.htm "Represents event log files generated by Event Monitoring. Use event log file data to analyze usage trends and user behavior in your Salesforce org. This object is available in API version 32.0 and later. The Interval and Sequence fields are available only in API version 37.0 and later.") - [_Salesforce Developers Blog_: Designing Force.com Applications That Avoid Hitting Concurrent Request Limits](https://developer.salesforce.com/blogs/engineering/2013/05/force-com-concurrent-request-limits.html " Salesforce Developers Blog: Designing Force.com Applications That Avoid Hitting Concurrent Request Limits - HTML (New Window)")