Skip to main content

​
Execution History

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

​
Filtering Logs

Narrow down your view with filters:
FilterOptions
StatusSuccess, Failed, Cancelled, Running
ProcessSelect specific process
Date RangeToday, last 7 days, last 30 days, custom
DriverFilter 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:
  • Execution status
  • Total duration
  • Number of actions
  • Trigger type (manual, API, scheduled)

​
Status Types

StatusMeaningColor
SuccessCompleted without errorsGreen
FailedEncountered an errorRed
CancelledStopped by userYellow
RunningCurrently executingBlue

​
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:
  1. Review what went wrong
  2. Click Retry to run again
  3. Or Edit Process to fix the issue first

​
Log Retention

Logs are retained based on your plan:
PlanRetention
Free7 days
Pro30 days
EnterpriseCustom
Screenshots and recordings may have different retention periods. Check your organization settings.

​
Exporting Logs

Export execution data for external analysis:
  1. Select the logs you want (or all)
  2. Click Export
  3. Choose format: CSV or JSON
  4. 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:
1

Check the Error Message

The timeline shows where the failure occurred and why
2

Review Screenshots

See the state of the desktop when the error happened
3

Watch the Recording

Sometimes seeing the full context reveals the issue
4

Check Driver Status

Was the driver machine having issues? Check Driver Management

​
Common Failure Patterns

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
The action took too long. Possible causes:
  • Slow network
  • Application not responding
  • Machine overloaded
Lost contact with the driver. Possible causes:
  • Network issue
  • Driver crashed
  • Machine rebooted

​
Next Steps

Analytics

See trends and patterns

Troubleshooting

Debug common issues