Job History

Job statuses, filtering, detail view, record-level details, and file downloads

A job is a single execution of a process. Every time your RPA tool executes a process. The Job History page gives you full visibility into every execution.

Job List

Navigate to Job History in the sidebar to see all jobs in the current account. The list shows:

- Process name — Which process was executed

- Status — Color-coded status indicator

- Started at — When the execution began

- Finished at — When the execution finished

- Duration — How long it took

- Robot — Which robot executed the job

- Source — Which RPA Tool

Filtering

Use the filters to narrow down jobs:

- Status — Success, Failed, Running, Cancelled

- Process — Show jobs for a specific process

- Date range — Filter by start date

- Search — Find jobs by process name or external job ID

Job Statuses

StatusColorDescription
BlueExecution is in progress
GreenCompleted without errors
Red
GrayExecution was cancelled or timed out

Summary Section

FieldDescription
Current status with visual indicator
Link to the parent process
Timestamps
Time from start to finish (seconds)
Which robot/agent executed the job
Source and target systems
Human-readable summary of what happened
Error details (for failed jobs)

Record Counts

MetricDescription
Number of records the process attempted to process
Records processed without errors
Records that encountered errors
Records intentionally skipped

Tags

Jobs can be tagged with arbitrary labels (e.g., "production", "daily", "urgent") for categorization. Tags are set via the Ingest API.

Custom Data

The data field contains arbitrary JSON metadata submitted via the API. This can include any information relevant to the execution — batch numbers, configuration parameters, environment details, etc.

Job Details (Per-Record)

If per-record details were submitted via the [Ingest API](/docs/run-details-and-files), the Details tab shows:

- Sequence — Processing order

- Record ID — Business identifier (e.g., invoice number)

- Record Name — Human-readable name

- Status — Success, Failed, or Skipped (per record)

- Result — Processing result

- Error Message — Per-record error details

- Processed At — When this specific record was processed

This provides full traceability — you can see exactly which records succeeded and which failed, with the exact error for each.

File Attachments

If files were attached to the job via the API, the Files tab shows:

- File name

- File size

- MIME type

- Upload date

- Download button

Click Download to retrieve the file (e.g., error logs, processed spreadsheets, reports).

Job Sources

Jobs come from two sources:

Synced Jobs

Created automatically by the [sync process](/docs/automatic-sync):

- Linked to processes by external ID

- Status mapped from the RPA tool's status values

- Duration and timestamps from the RPA tool

API Jobs

Created via the [Ingest API](/docs/reporting-runs):

- Can include full record-level details

- Can have file attachments

- Support arbitrary metadata and tags