Run history lists every run of an automation with its start time, status, duration and the number of actions it executed. Open the automation and select History to read it; Administrators and Solution Managers also receive an email and an in-app notification when a run fails.
Plan Availability | All plan types. Run history is kept for 1 year on Team, 2 years on Professional and 3 years on Enterprise and Signature. |
Permissions | Administrators and Solution Managers: open automation run history and receive error notifications. |
Platform | Web |
Related Reading |
My automation failed or did not run: check these five things, in order
Administrators and Solution Managers can open History and change the automation. If you have neither role, send this page and the record name to the person who manages the solution.
History. Open the automation from Automations in the Solution menu and select History. Each run shows when it started, its status, its duration and the number of actions it used; select Details on a failed run to see the step that failed and its error message. See How do I open an automation's run history?.
No run listed. The trigger never fired: the automation is off, or the record already matched the condition. The checks are in Fix an automation that did not run.
Every automation started failing at once. The workspace reached its monthly automation action limit, and every run fails with Usage Limit Reached until the monthly reset, or until an Administrator turns on the Auto-Increment toggle in Workspace Administration > Usage. See Automation Limits.
A failed run with an error. Read the error on the run. The meanings are in What do the common errors mean? and the fixes in Common Automation Error Troubleshooting.
An expired credential. A run that failed because of an expired credential keeps the old credential on a retry. Reconnect the account and trigger a fresh run instead of selecting Rerun this automation; see Common Automation Error Troubleshooting.
Still stuck: select the chat button in the lower-right corner of SmartSuite. The panel shows the current service status under Search for help; to reach support, select Ask a question. Include the automation link (the three-dot menu, then Copy Link), the start time of the run, or the time it should have run, and the link to the record. To copy it, open the record and select the link icon next to its number, or choose Copy Link in the record's three-dot menu. The full fix guide is Fix an automation that did not run.
What is run history?
Run history is the log of an automation's past executions. Use it to confirm that a new automation works, to measure how long runs take and to find the step that failed.
How do I open an automation's run history?
In the Solution menu, select Automations and open the automation.
Select History.
Read the list of runs. Each run shows Started, Status (Success, Error or Running), Duration and Actions (the number of actions the run used).
Select Details on a run. The top line shows Run successfully or Failed to run with the date and time; a failed run also has a Rerun this automation button. Below it, the trigger and each action are listed with a Success or Error badge. Expand one to see the records it worked on; a failed step shows its error message and a Learn how to fix common issues link.
Some failed runs cannot be rerun, for example when the webhook request that should have started the run was rejected. Hovering Rerun this automation then shows This automation cannot be re-run., so trigger a new run instead.
How long is run history kept?
Plan | Retention |
Team. | 1 year. |
Professional. | 2 years. |
Enterprise. | 3 years. |
Signature. | 3 years. |
Who is told when an automation fails?
Workspace Administrators and the Solution Managers of the solution receive an email with the error details and a SmartSuite notification for each failed run.
What do the common errors mean?
The error is shown on the failed step in the run's Details. The full list of errors, what they mean and how to fix them is in Common Automation Error Troubleshooting.
Frequently asked questions
Where do I see how many automation actions my workspace has used this month?
Where do I see how many automation actions my workspace has used this month?
Administrators select the workspace name in the upper-left corner and choose Workspace Usage. The Automation Actions tab shows the actions used this month against the plan allowance and the days left until the next cycle, and has the Auto-Increment toggle for extra 1,000-action blocks. See Automation Limits for the allowances.
Can I re-run a failed automation?
Can I re-run a failed automation?
Yes, in most cases. Open the run in History, select Details and select Rerun this automation. Some runs cannot be rerun; the button then shows This automation cannot be re-run. A run that failed because of an expired credential keeps the old credential, so reconnect the account and trigger a fresh run instead of a retry.
Why did every automation in the workspace start failing at the same time?
Why did every automation in the workspace start failing at the same time?
The workspace reached its monthly automation action limit. Administrators are notified at 90 percent and 100 percent of the limit. Runs fail with Usage Limit Reached until the monthly reset, or until the Auto-Increment toggle for extra runs is on in Workspace Administration > Usage. See Automation Limits.
Last verified 29 Oct 2026.