---
schema_version: "1"
id: 754b800146f22415c138c924b7fc1ac01adf1eea15cea65aae173d117d2525ba
title: Apex Execution 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_apexexecution.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_apexexecution.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 5b7bd64160a7045219e875e002653124f7cabe52e64ff520806b847443cbb858
description: Apex Execution events contain details about Apex classes that are used.
---
# Apex Execution Event Type

Apex Execution events contain details about Apex classes that are used.

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

<table class="featureTable sort_table" summary=""><tbody class="tbody"><tr><td class="entry"><strong class="ph b">Field</strong></td><td class="entry"><strong class="ph b">Details</strong></td></tr><tr><td class="entry"><span class="keyword parmname">BOT_IDENTIFIER</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">string</dd><dt class="dt dlterm">Description</dt><dd class="dd">The ID of the bot.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">BOT_SESSION_IDENTIFIER</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">string</dd><dt class="dt dlterm">Description</dt><dd class="dd">The bot session ID.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">CALLOUT_TIME</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd">Time spent waiting on webservice callouts, in milliseconds.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">CLIENT_IP</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from AppExchange) is shown as “Salesforce.com IP”. If the user’s session context isn't available, this field returns a blank value.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">CPU_TIME</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd">The CPU time in milliseconds used to complete the request. This field indicates the amount of activity taking place in the app server layer.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">DB_TOTAL_TIME</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd" id="db-total-time-Apex-desc"><a name="db-total-time-Apex-desc"></a>Time (in milliseconds) spent waiting for database processing in aggregate for all operations in the request. Compare this field to <span class="keyword parmname">CPU_TIME</span> to determine whether performance issues are occurring in the database layer or in your own code.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">ENTRY_POINT</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The entry point for this Apex execution.</dd><dt class="dt dlterm">Example</dt><dd class="dd"><ul class="ul bulletList"><li class="li"><samp class="codeph nolang">GeneralCloner.cloneAndInsertRecords</samp></li><li class="li"><samp class="codeph nolang">VF- /apex/CloneUser</samp></li></ul></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">EVENT_TYPE</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="event-type-desc"><a name="event-type-desc"></a>The type of event.</span> The value is always <samp class="codeph nolang">ApexExecution</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">EXEC_TIME</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd" id="exec-time-Apex-desc"><a name="exec-time-Apex-desc"></a>The end-to-end Apex execution time (in milliseconds).</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">IS_LONG_RUNNING_REQUEST</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Boolean</dd><dt class="dt dlterm">Description</dt><dd class="dd">Indicates whether the request is counted against your org’s concurrent long-running Apex request limit (<samp class="ph systemoutput">true</samp>) or not (<samp class="ph systemoutput">false</samp>).<div class="box message info"><div class="inner"><div class="bd"><div class="media"><img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png" alt="Note"><div class="mediaBd"><h4 class="mbs">Note</h4><p>Asynchronous Apex jobs (batch, queueable, scheduled, and future), background processes, and bulk API requests aren’t counted against the concurrent long-running limit.</p></div></div></div></div></div></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">LOGIN_KEY</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="login-key-desc"><a name="login-key-desc"></a>The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring.</span></dd><dd class="dd"><span class="ph" id="login-key-ex"><a name="login-key-ex"></a>For example: <samp class="codeph nolang">GeJCsym5eyvtEK2I</samp>.</span></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">NUMBER_SOQL_QUERIES</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd">The number of SOQL queries that were executed during the event.<p class="p">This value is the aggregate across all namespaces, and can exceed the per-namespace limits. For test executions, the aggregate total value across all test methods executed in the request is used. If you’re using this value to track limit consumption, consider filtering out test execution quiddities (indicated by the QUIDDITY field).</p></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">ORGANIZATION_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Id</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="organization-id-desc"><a name="organization-id-desc"></a>The 15-character ID of the organization.</span></dd><dd class="dd"><span class="ph" id="organization-id-ex"><a name="organization-id-ex"></a>For example: <samp class="codeph nolang">00D000000000123</samp>.</span></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">PLANNER_IDENTIFIER</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">string</dd><dt class="dt dlterm">Description</dt><dd class="dd">The ID of the agent planner.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">QUIDDITY</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The type of outer execution associated with this event.</dd><dt class="dt dlterm">Example</dt><dd class="dd"><ul class="ul bulletList"><li class="li"><span class="keyword parmname">A</span>–ACS Batch Apex</li><li class="li"><span class="keyword parmname">B</span>–Bulk API and Bulk API 2.0</li><li class="li"><span class="keyword parmname">BA</span>–Start method of a Batch Apex job</li><li class="li"><span class="keyword parmname">C</span>–Scheduled Apex</li><li class="li"><span class="keyword parmname">CI</span>–Commerce Integration</li><li class="li"><span class="keyword parmname">DL</span>– Discoverable Login page</li><li class="li"><span class="keyword parmname">E</span>–Inbound Email Service</li><li class="li"><span class="keyword parmname">F</span>–Future</li><li class="li"><span class="keyword parmname">FC</span>–Function Callback</li><li class="li"><span class="keyword parmname">H</span>–Apex REST</li><li class="li"><span class="keyword parmname">I</span>–Invocable Action</li><li class="li"><span class="keyword parmname">K</span>–Quick Action</li><li class="li"><span class="keyword parmname">L</span>–Lightning</li><li class="li"><span class="keyword parmname">M</span>–Remote Action</li><li class="li"><span class="keyword parmname">P</span>–Not used in API version 63.0 and later.</li><li class="li"><span class="keyword parmname">PEPC</span>–Platform Event Publish Callback</li><li class="li"><span class="keyword parmname">PI</span>–Post install script for a managed package</li><li class="li"><span class="keyword parmname">Q</span>–Queueable</li><li class="li"><span class="keyword parmname">QTXF</span>–Transaction Finalizer for Queueable</li><li class="li"><span class="keyword parmname">R</span>–Synchronous uncategorized (which is where all transactions not specified elsewhere end up)</li><li class="li"><span class="keyword parmname">S</span>–QueryLocator Batch Apex (Batch Apex jobs run faster when the start method returns a QueryLocator object that doesn't include related records via a subquery. See Batch Apex Best Practices in <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.264.0.apexcode.meta/apexcode/apex_batch_interface.htm#apex_batch_best_practices" target="_blank" title="HTML (New Window)">Using Batch Apex</a>.)</li><li class="li"><span class="keyword parmname">TA</span>–Tests Async</li><li class="li"><span class="keyword parmname">TD</span>–Tests Deployment</li><li class="li"><span class="keyword parmname">TS</span>–Tests Synchronous</li><li class="li"><span class="keyword parmname">UD</span>–Undefined is the default when an event hasn’t been assigned a more descriptive quiddity.</li><li class="li"><span class="keyword parmname">V</span>–Visualforce</li><li class="li"><span class="keyword parmname">W</span>–SOAP Webservices</li><li class="li"><span class="keyword parmname">X</span>–Execute Anonymous</li></ul><div class="box message info"><div class="inner"><div class="bd"><div class="media"><img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png" alt="Note"><div class="mediaBd"><h4 class="mbs">Note</h4><p>Implementations of the Process.Plugin interface use the quiddity value <strong class="ph b">R</strong>.</p></div></div></div></div></div></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">REQUEST_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="request-id-desc"><a name="request-id-desc"></a>The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same <span class="keyword parmname">REQUEST_ID</span>.</span></dd><dd class="dd">For example: <samp class="codeph nolang">3nWgxWbDKWWDIk0FKfF5DV</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">RUN_TIME</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="run-time-Apex-desc"><a name="run-time-Apex-desc"></a>The amount of time that the request took in milliseconds.</span><p class="p">Requests with a value over five seconds are considered long-running requests for the purposes of the Concurrent Long-Running Apex Limit.</p><div class="box message info"><div class="inner"><div class="bd"><div class="media"><img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png" alt="Note"><div class="mediaBd"><h4 class="mbs">Note</h4><p>HTTP callout processing time isn't included when calculating the 5-second limit. We pause the timer for the callout and resume it when the callout completes.</p></div></div></div></div></div></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">SESSION_KEY</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="session-key-desc"><a name="session-key-desc"></a>The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started.</span></dd><dd class="dd">For example: <span class="ph" id="session-key-ex"><a name="session-key-ex"></a><samp class="codeph nolang">d7DEq/ANa7nNZZVD</samp>.</span></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">TIMESTAMP</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="timestamp-desc"><a name="timestamp-desc"></a>The access time of Salesforce services in GMT.</span></dd><dd class="dd"><span class="ph" id="timestamp-ex"><a name="timestamp-ex"></a>For example: <samp class="codeph nolang">20130715233322.670</samp>.</span></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">TIMESTAMP_DERIVED</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">DateTime</dd><dt class="dt dlterm">Description</dt><dd class="dd">The access time of Salesforce services in ISO8601-compatible format (<samp class="codeph nolang">YYYY-MM-DDTHH:MM:SS.sssZ</samp>).</dd><dd class="dd">For example: <samp class="codeph nolang">2015-07-27T11:32:59.555Z</samp>. Timezone is GMT.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">URI</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The URI of the page that’s receiving the request.</dd><dd class="dd">For example: <span class="keyword parmname">/home/home.jsp</span>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">URI_ID_DERIVED</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">ID</dd><dt class="dt dlterm">Description</dt><dd class="dd">The 18-character case insensitive ID of the URI of the page that’s receiving the request.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">USER_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Id</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="user-id-desc"><a name="user-id-desc"></a>The 15-character ID of the user who’s using Salesforce services through the UI or the API.</span></dd><dd class="dd"><span class="ph" id="user-id-ex"><a name="user-id-ex"></a>For example: <samp class="codeph nolang">00530000009M943</samp></span></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">USER_ID_DERIVED</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Id</dd><dt class="dt dlterm">Description</dt><dd class="dd">The 18-character case insensitive ID of the user who’s using Salesforce services through the UI or the API.</dd><dd class="dd"><span class="ph" id="user-id-derived-ex"><a name="user-id-derived-ex"></a>For example: <samp class="codeph nolang">00590000000I1SNIA0</samp></span>.</dd></dl></td></tr></tbody></table>

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