Get detailed insights into how your automations operate by checking the run log. Each time an automation is triggered, the run log presents vital information such as the status of each run, how it performed, and whether there were any issues along the way.
This helps you monitor the success of your automations, identify potential problems, and ensure your workflows run smoothly. For example, if a customer reports not receiving a confirmation email, you can quickly check the logs to see if the automation ran as expected.
Where can I find an automation's run log?
You can access a run log from the summary panel under the activity section. This will redirect you to the automation builder, where you can see a panel with the run log table. There, you can navigate between different runs and view their details.
Go to Automations in your site's dashboard.
Hover over the relevant automation and click View Summary.
Click View run log in the activity section.
Key features and benefits of the run log
Run logs give you a detailed record of each automation run, including the status, start time, and duration. This allows you to monitor performance and quickly identify any issues. They also help you understand how edits or changes to your automations impact their behavior over time, giving you the visibility needed to keep everything running smoothly and efficiently.
In addition to these benefits, the run log offers several key features to help you track and manage your automations:
Detailed records: Each run includes information like its status (e.g. In progress, Ended), duration, and completion time. This helps you gauge whether your automations are performing as expected.
Tracking versions by publish date: Run logs are sorted by the date and time an automation was last published. Whenever you edit and re-publish an automation, the updated version is reflected in the logs, making it easy to identify what changes may have affected the results of your automation.
Error insights: Statuses like 'Ended with Issues' or 'Failed' provide clear indications when something doesn't work as expected. While some issues may be due to internal technical errors, others might occur due to the automation's configuration.
Did you know?
Logs for completed runs are saved for 30 days, while logs for ongoing runs are stored for up to 1 year. This allows you ample time to review and analyze your automation’s activity history.
Understanding statuses
Each automation run provides information about its progress and actions. Understanding these statuses helps you follow up on automation runs and address any issues promptly.
Run statuses
Run statuses help describe how each automation was executed, its progress, and any potential issues:
In Progress: The run is currently executing.
Ended: All actions in the run have completed.
Ended with issues: The run finished, but one or more actions failed.
Failed: The run couldn’t execute due to technical issues. This means that no action was performed.
Skipped: A run is skipped when a task is set to run once per user, or when the data doesn't match the trigger settings. For a full breakdown of skip reasons, see the FAQ section below.
Cancelled: The run was stopped while in progress (e.g., automation deactivated). For a full breakdown of cancellation reasons, see the FAQ section below.
Step statuses
Each individual step within an automation has its own status indicating its outcome:
Completed: The step has finished.
In Progress: The step is currently executing.
Failed: The step couldn’t perform due to technical issues.
Cancelled: The step wasn’t performed because the run was stopped.
FAQs
Here are some common questions about run logs:
How can I fix runs or actions that 'Failed'?
Failed runs or actions usually happen because of technical issues. They should resolve on their own.
If they fail repeatedly, try editing the automation to make sure everything is configured as expected. After editing your automation if your runs or actions still fail, let us know the corresponding run IDs so that we can investigate further.
Why was my run skipped?
A run is skipped when the initial conditions for the automation are not met at the very start. There are a few reasons this can happen:
Data didn't match criteria: The trigger event occurred, but the specific data didn't meet the logic you set. For example, if your automation is set up for a specific form under the 'Form Submitted' trigger (rather than 'any' form), submissions from other forms will be skipped.
Run once per person: Your trigger is configured to allow a contact to enter the workflow only once. If the same contact triggers the automation again after already completing it, the subsequent run is skipped.
Technical issue: An unexpected error occurred at the moment of triggering, preventing the run from initializing. If you're seeing a high frequency of technical issue skips, let us know the corresponding run IDs so that we can investigate further.
Why was my run cancelled?
A run is cancelled when an active automation is interrupted after it has already begun. This usually happens because something changed while steps were still pending. Here are the most common reasons:
Changes to the triggering event: The original data that started the automation was updated or deleted, making the remaining steps irrelevant. For example, if an automation uses the 'Session Booked' trigger with a delay step, and the session is cancelled during that delay, the run will be cancelled since the following actions are no longer relevant.
Automation deactivated: The automation was manually deactivated while the run was in progress. When an automation is deactivated, all currently active runs are stopped.
Privacy and data protection: The contact unsubscribed, requested data deletion, or updated their consent settings (e.g. GDPR) while the run was in progress. The system automatically cancels the run to ensure legal compliance.
Technical issue: An unexpected error occurred while the automation was in progress, preventing it from completing. If you're seeing a high frequency of technical issue cancellations, let us know the corresponding run IDs so that we can investigate further.
How long are the run logs saved for?
The amount of time logs are saved for is based on the duration and status of the automation.
Logs for runs that are in progress are saved for up to a year. Once runs are completed (e.g. 'Ended', 'Ended with issues', 'Failed', 'Cancelled'), their logs are then saved for another 30 days.
If a run is in progress for more than a year, the log will be deleted after 1 year. However, the run itself will technically continue executing as expected.
Why can’t I find a specific run log?
If a log is missing, it could be because:
The run was completed more than 30 days ago and its log has been deleted.
The run is ongoing for longer than a year and has exceeded the 1-year storage limit.
The run was triggered before April 1, 2025 (only runs triggered on or after this date are recorded in the logs).
Does an 'Ended' run status mean that all actions executed successfully?
No. An 'Ended' status means that all actions were processed but it doesn't confirm delivery.
For example, an automation with the 'Send an Email' action that has the 'Ended' status means that the email was sent. But it doesn't confirm that the email was delivered. It could be that the email bounced and never reached certain recipients.
Can I check how long a run has had its current status?
Yes. Each log includes a 'Status Updated' timestamp, showing the exact date and time the status last changed.
My in-progress run isn't on the list as it's been more than a year. Will it still execute my actions?
Yes, even though the run does not appear on the run log anymore, it will technically continue executing as expected.
Why is the version published on a date I didn't work on my site?
This can happen with an app automations where a new version published by the app that added the automation instead of a manual update that you published.
How can I see the input or output data of a specific step?
You can see the input and output data of a specific step as part of your run log:
Go to Automations in your site's dashboard.
Hover over the relevant automation and click View Summary.
Click View run log in the activity section.
Click the relevant run under Run log.
Click on a step from the flow.
Click the Step input and output icon
on the left side of the panel.
Click the Step input tab or Step output tab to view the data you want to see.
Can I repeat a specific run from the run log?
Yes. You can trigger a specific run directly from the run log. This is useful if a run failed, ended with issues, or if you simply need the automation to execute again for the same contact or record.
To trigger an automation again:
Go to Automations in your site's dashboard.
Hover over the relevant automation and click View Summary.
Click View Run Log in the activity section.
Hover over the run you want to repeat and click the Rerun icon
.
Note: Repeating a run creates a new run. It doesn't resume or modify the original run log entry.
This article is credited to the Wix team - https://support.wix.com/ and we thank them for that!