Run Logs

Execution History

The Run Logs page shows all past automation executions across your organization.

Filtering Logs

Narrow down your view with filters:

Filter	Options
Status	Success, Failed, Cancelled, Running
Process	Select specific process
Date Range	Today, last 7 days, last 30 days, custom
Driver	Filter by machine

Log List View

Each log entry shows:

Process name - Which automation ran
Status badge - Success/Failed/Cancelled
Duration - How long it took
Timestamp - When it ran
Driver - Which machine executed it

Viewing Run Details

Click any log entry to see full details:

Summary
Timeline
Screenshots
Recording

Execution status
Total duration
Number of actions
Trigger type (manual, API, scheduled)

Step-by-step trace of the execution:

15:32 - Started execution
15:35 - Connected to driver-01
15:38 - Action: Open Excel
15:42 - Action: Click File menu
15:45 - Action: Select Open
...
18:22 - Completed successfully

Status Types

Status	Meaning	Color
Success	Completed without errors	Green
Failed	Encountered an error	Red
Cancelled	Stopped by user	Yellow
Running	Currently executing	Blue

Searching Logs

Use the search bar to find logs by:

Process name
Error messages
Action descriptions

Search for specific error messages like “element not found” to identify patterns in failures.

Bulk Actions

Select multiple logs to:

Delete - Remove selected logs
Export - Download as CSV/JSON

Re-running Failed Executions

From a failed execution’s detail page:

Review what went wrong
Click Retry to run again
Or Edit Process to fix the issue first

Log Retention

Logs are retained based on your plan:

Plan	Retention
Free	7 days
Pro	30 days
Enterprise	Custom

Screenshots and recordings may have different retention periods. Check your organization settings.

Exporting Logs

Export execution data for external analysis:

Select the logs you want (or all)
Click Export
Choose format: CSV or JSON
Download the file

CSV Format

id,process_name,status,duration_ms,started_at,finished_at,driver_id
run_123,Sales Report,success,180000,2024-01-15T10:15:32Z,2024-01-15T10:18:32Z,driver-01

JSON Format

{
  "id": "run_123",
  "process_name": "Sales Report",
  "status": "success",
  "duration_ms": 180000,
  "started_at": "2024-01-15T10:15:32Z",
  "finished_at": "2024-01-15T10:18:32Z",
  "driver_id": "driver-01",
  "actions": [...]
}

Debugging Failed Runs

When an execution fails:

Check the Error Message

The timeline shows where the failure occurred and why

Review Screenshots

See the state of the desktop when the error happened

Watch the Recording

Sometimes seeing the full context reveals the issue

Check Driver Status

Was the driver machine having issues? Check Driver Management

Common Failure Patterns

Element not found

The agent couldn’t locate a UI element. Possible causes:

Application didn’t open in time
UI changed since last run
Element is behind a popup

Timeout

The action took too long. Possible causes:

Slow network
Application not responding
Machine overloaded

Connection lost

Lost contact with the driver. Possible causes:

Network issue
Driver crashed
Machine rebooted

Next Steps

Analytics

See trends and patterns

Troubleshooting

Debug common issues

Get Started

Getting Started

Dashboard

Agent Execution

RPA Automation

Public API

VM Management

Driver

Troubleshooting

Execution History

Filtering Logs

Log List View

Viewing Run Details

Status Types

Searching Logs

Bulk Actions

Re-running Failed Executions

Log Retention

Exporting Logs

CSV Format

JSON Format

Debugging Failed Runs

Common Failure Patterns

Next Steps

Analytics

Troubleshooting

​Execution History

​Filtering Logs

​Log List View

​Viewing Run Details

​Status Types

​Searching Logs

​Bulk Actions

​Re-running Failed Executions

​Log Retention

​Exporting Logs

​CSV Format

​JSON Format

​Debugging Failed Runs

​Common Failure Patterns

​Next Steps

Analytics

Troubleshooting

Execution History

Filtering Logs

Log List View

Viewing Run Details

Status Types

Searching Logs

Bulk Actions

Re-running Failed Executions

Log Retention

Exporting Logs

CSV Format

JSON Format

Debugging Failed Runs

Common Failure Patterns

Next Steps