Automations Logs
This log shows the status and details of Automation runs in your site. Check the Automation's version before interpreting a result: a v1 run performs one action type, while a v2 run can contain several connected nodes with their own error-handling rules.
Each entry identifies the Automation and its run, start time, and status. V1 run logs show the file operations performed. V2 run detail shows the nodes executed and the items each received and produced. Informational messages and error details help explain failures in either version.
Automation run records and their detailed logs are retained for 30 days from the run record's creation, then automatically removed. This does not delete the Automation or files it saved in your folders. File actions performed by an Automation also appear in History Logs, which have a separate retention period.
The site-wide log and its dedicated logging API endpoints require a Site Administrator because the logging service cannot filter entries to each user's permitted folders or Workspaces. This also limits access to live details while a run is in progress. Folder Admins who can access a v1 Automation can read its saved run log after completion, including when that Automation is site-owned.
Details Recorded in Automations Logs
The following columns describe v1 runs. For v2's node-level results and retry links, use Run Logs (v2) and Run Detail (v2).
| Column | Details |
|---|---|
| Date | Start time of the automation run. |
| Automation ID | ID of the Automation. Clicking the Automation ID will take you to the Automation Details page, where you can view all runs associated with that particular automation. |
| Automation Run ID | ID of a specific run of the Automation. Clicking the Automation Run ID will take you to the detailed logs for each action performed. |
| Operation | Type of the Automation. Possible values include Copy, Move, Delete, Create Folder, Import Files, and Run Sync. |
| Path | Source file path. When filtering the Path, delimit it with slashes /, excluding both the start and end slashes. Maximum length: 5000 characters. |
| Destination Path | Destination path for move, copy and import file automations. |
| Status | Current state or final outcome of the automation run. See more details below in Automations Run Status. |
| Message | Information message for this specific run. |
| Error | Error details in case the automation encounters a failure. |
Automations Run Status
The Status value indicates the current state or final outcome of the Automation run. The table below describes v1 statuses. Some statuses are visible only when you browse the Automation runs in detail, down to the Run Log Details, by opening the Automation ID or Automation Run ID.
V1 run retries replan work from the files that currently match, excluding matching operations that already succeeded or were skipped. V2 retries resume at the failed node. Use the retry rules for the run's version when deciding what a retry will repeat.
For v2, Error Handling also determines the run's result. A failed item may be routed to an Error path or stop the run; a Failure status does not mean that every earlier node failed. Use the v2 status definitions to interpret those runs.
| Status | Description |
|---|---|
| Failure | A final outcome of the automation run. The automation run failed to perform its action on all items. |
| Partial Failure | A final outcome of the automation run. The automation run failed to perform its action on some items while actions on other items were successful. |
| Queued | The automation has been prepared to run. |
| Running | The automation is currently in progress planning, validating, or executing. |
| Skipped | A final outcome of the automation run. The run completed without doing meaningful work and was skipped for the reason shown in the Details, which commonly occurs when the automation is disabled, prerequisites are missing, or an operation is intentionally skipped. |
| Info | Displays the message "No operations performed" when the automation run ends with this status. |
| Success | A final outcome of the automation run. The automation run successfully performed its action on all items. |