Subscribe

UiPath Insights

The UiPath Insights Guide

Insights Data Model

This page details the Jobs, Queues, and Robot Logs data that Insights ingests. For information around the Manual Values explores, see Templates.

The data is surfaced via Explores, which you can think of as a general entity that corresponds to the fields within it. For example, to build dashboards around Orchestrator jobs, pick the Jobs Explore. Each Explore surfaces views that contain the respective data. You can access related data from within Explores, i.e. Robot Logs are accessible from the Jobs Explore, etc.

DimensionsDescription
Process VersionThe version number of the process the job belongs to.
Robot NameThe name of the Robot that executed the job.
Robot TypeThe type of robot that executed the job. The available options are:
Attended
Unattended
Host Machine NameThe name of the machine where the robot executed the job.
Job IdThe row ID of the job event in the Orchestrator database
Job StateThe status of the job. See Job States for all available states and their descriptions.

Note: Insights only ingests terminal states (i.e. successful, stopped, and faulted).
User NameThe name of the Orchestrator user that ran the job.
User TypeThe type of user type that executed the job. The available options are:
RPA Developer
RPA Developer Pro
Citizen Developer
Attended User
Creation TimeThe time when the job was created.
Start TimeThe time when execution of the job began.
End TimeThe time when execution of the job finished.
Job SourceThe triggering event for job execution. The available options are:
Manual
Schedule
Other
Environment NameThe Environments where the job was executed.
Process NameThe name of the process.
Process Display NameThe display name of the process as entered in Orchestrator.
Job Duration in SecondsThe duration, in seconds, of the job execution. Computed as the difference between StartTime and EndTime.
FolderFolder where the job is defined.
MeasuresDescription
Faulted JobsThe number of jobs with the Faulted status.
Faulted RateThe % of jobs with the Faulted status compared to the total number of jobs.
Processes RanThe number of processes that have reached a final status of Successful, Faulted, or Stopped.
Success RateThe % of jobs with the Successful status compared to the total number of jobs.
Successful JobsThe number of jobs with the Successful status.
Time in Pending in SecondsThe amount of time all jobs spent in the Pending and Resumed states, meaning how long it took from the moment the job was queued until it actually ran on the robot (see Job States).
Total Suspended Time in SecondsThe time of jobs, in seconds, spent in a suspended state in seconds (see Job States). You can use this measure to calculate the total time spent on a particular process by subtracting the time spent in a suspended state, in long-running workflows.
Total Run Time in SecondsThe total processing time of all jobs in seconds.

📘

Note

If using queue encryption via Orchestrator, reporting analytics on Specific Data, Analytics and Output data fields will not be possible. If this feature is enabled, any dashboards using these fields will not have the data available.

Specific Data, Analytics and Output data fields are deprecated starting with 22.10. You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables.

See Insights deprecation timeline

DimensionsDescription
PriorityThe priority of the queue item defined when setting its properties from Studio.
Queue Item IdThe auto-incremented row ID of the queue item in the Orchestrator database.
Queue NameThe name of the queue.
Processing StatusThe status of the queue item. The available options are:
Successful
Failed
Abandoned
Review StatusThe review status of the queue item.
Robot NameThe name of the robot that processed the queue item.
Robot TypeThe type of robot that executed the job. The available options are:
Attended
Unattended
NonProduction
Testing
Other
Creation DateThe time the queue item was created.
Start Processing DateThe time the robot began processing the queue item.
End Processing DateThe time the robot finished processing the queue item.
Transaction Duration in SecondsThe processing time, in seconds, of the queue item. Computed as the difference between Start Processing Date and End Processing Date.
Seconds In Previous AttemptsThe time, in seconds, of all attempts to process the transaction.
Retry NumberThe number of times the processing of the transaction has been attempted. For the first attempt, 0 is displayed.
Defer DateThe earliest date and time the queue item is available for processing. If empty, it can be processed immediately.
Due DateThe latest date and time which the queue item must be processed by. If empty, it can be processed at any time.
ProgressCustom progress information for queue items with status InProgress.
Processing Exception TypeThe type of the exception thrown when processing fails. The available exception types are:
ApplicationException
BusinessException
Processing Exeption ReasonThe details of the exception thrown when processing fails.
ReferenceThe user-specified value for identification purposes provided when adding the queue item in Studio.
Output
Deprecated and no longer supported after the 2022.10 release.

You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables.

See Insights deprecation timeline.
A collection of key value pairs containing custom data upon successful processing associated with the transaction. See here for details.
Analytics Data
Deprecated and no longer supported after the 2022.10 release.

You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables.

See Insights deprecation timeline.
A collection of key value pairs containing custom data for analytics purposes associated with the transaction. See here for details.
Specific Data
Deprecated and no longer supported after the 2022.10 release.

You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables.

See Insights deprecation timeline.
A collection of key value pairs containing custom data associated with the transaction. See here for details.
Reviewer User NameThe user name of the assigned reviewer, if any.
Queue IdThe numerical identifier of the queue, comprised of QueueName, OrganizationUnitId.
FolderThe folder on which a queue item was executed.
MeasuresDescription
Avg Queue Wait Time in SecondsHow long it takes, on average, between when all queue items were created and when a robot started processing them.
First Pass Yield % Per QueueThe percentage of time that the queue item was successful on its first try at processing (retry number =0).
Queue CountThe number of queues with data processed on this tenant.
Queue Item CountThe number of queue items processed on this tenant.

DataDescription
IdThe auto-incremented row ID of the log in the Orchestrator database.
Timestamp DateThe time the logging was executed.
Machine IdThe Id of the machine that generated the log message.
Machine NameThe Machine Name.
Process NameThe name of the process that generated the log message.
Process VersionThe version number of the process the job belongs to.
Windows IdentityThe user under which the robot generating the log message was logged in.
Robot NameThe name of the robot that generated the log message.
Raw Message
Deprecated and no longer supported after the 2023.4 release

See Insights deprecation timeline
JSON output from the execution log.
Transaction IdThe key of the associated queue item.
MessageThe logged message.
Level
Deprecated and no longer supported after the 2022.10 release

See Insights deprecation timeline
The severity level at which the message was logged. See Logging Levels for details.
Log TypeGenerated according to the process designed by the user in Studio, when using the Log Message activity or the Write Line activity.
These logs have a value of User.
Queue NameThe name of the queue.
File NameThe name of the file that created the automation.

Updated about a month ago


Insights Data Model


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.