---
schema_version: "1"
id: b87cf317e34551093462f757bfeae95478f641325162f95ecae15d0610e97178
title: Time-Based Workflow 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_timebasedworkflow.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_timebasedworkflow.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 87ef775ac4ce4a06334fc576f69794b741c6039e95dcc067ff47793e46c47596
description: Time-Based Workflow events contain details about queue activity monitoring.
---
# Time-Based Workflow Event Type

Time-Based Workflow events contain details about queue activity monitoring.

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 the [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

![Note](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png)

#### Note

Time-Based Workflow events only support workflow rules, and not flow scheduled path time-queue records. Event logs do not show flow scheduled path time-queue records.

<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">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”.</dd><dd class="dd">For example: <samp class="codeph nolang">96.43.144.26</samp>.</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">DATA</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 record details of time queue activity.</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">The type of event. The value is always <samp class="codeph nolang">TimeBasedWorkflow</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">LOG_GROUP_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">Marks log records that are committed or rolled back.</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">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.</dd><dd class="dd">For example: <samp class="codeph nolang">GeJCsym5eyvtEK2I</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">NUMBER_OF_RECORDS</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 processed records.</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">The 15-character ID of the organization.</dd><dd class="dd">For example: <samp class="codeph nolang">00D000000000123</samp>.</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">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>.</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">The amount of time that the request took in milliseconds.</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">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.</dd><dd class="dd">For example: <samp class="codeph nolang">d7DEq/ANa7nNZZVD</samp>.</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">The access time of Salesforce services in GMT.</dd><dd class="dd">For example: <samp class="codeph nolang">20130715233322.670</samp>.</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">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">The type of time-based workflow event.<ul class="ul bulletList"><li class="li"><samp class="codeph nolang">UIDEL</samp>—An entry was deleted from the Time-Based Automations page in Setup.</li><li class="li"><samp class="codeph nolang">ERRDEL</samp>—An entry was deleted from the workflow queue, because there was an error reading the record that triggered the workflow rule. The associated time-dependent actions weren’t processed.</li><li class="li"><samp class="codeph nolang">DELETE</samp>—An entry was deleted from the workflow queue, because it’s no longer relevant. For example, the criteria are no longer met by the associated record. If the evaluation date for the entry changed, the entry is re-added with the updated evaluation date.</li><li class="li"><samp class="codeph nolang">PROC</samp>—An entry was deleted from the workflow queue after processing a time-dependent action.</li></ul></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">The 15-character ID of the user who’s using Salesforce services through the UI or the API.</dd><dd class="dd">For example: <samp class="codeph nolang">00530000009M943</samp></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">For example: <samp class="codeph nolang">00590000000I1SNIA0</samp>.</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.")