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 its start time, status, duration and the actions executed; open a failed run for the error message. See How do I open an automation's run history?.
No run listed. The trigger never fired: the automation is off, the record already matched the condition, or the workspace reached its monthly action limit. The checks are in Fix an automation that did not run.
Every automation stopped at once. The workspace reached its monthly automation action limit. Automations resume at the monthly reset, or at once when the auto-billing toggle for extra runs is on. 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 Re-run Automation; see Common Automation Error Troubleshooting.
Still stuck: select the chat button in the lower-right corner of SmartSuite. The last block of the panel shows the service status, and Send a message in the same panel reaches support. Include the automation link (the three-dot menu, then Copy Link), the start time of the run and the record name. 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 its Start Time, Status (success, error or running), Duration and Actions Executed.
Open a run to see each action and its error message, if any.
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?
Error | Meaning |
Build record missing inputs. | A field used as an input to an action was deleted. |
Action inputs could not be generated. | An action has invalid or missing inputs, usually because a field was deleted. |
Bad Gateway. | The server did not respond. |
Gateway Timeout. | The server did not respond in time, or the request ran too long. |
Action Fail. | An external service returned an error, for example Slack or Twilio. |
Missing record ID in inputs. | The record to update was not found. |
Invalid phone number. | The Twilio action received a phone number it cannot use. |
Bad Request. | Invalid data was sent to the server. |
Unable to find choice. | A Select field does not have the option the action tried to set. |
No emails to send to. | No valid email address reached an action that sends email. |
Read the full list of fixes 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 open Workspace Administration and select the Usage tab. It shows the actions used against the plan limit and any add-on purchases; see Automation Limits for the limits and the overage add-on.
Can I re-run a failed automation?
Can I re-run a failed automation?
Yes. Open the run in History and select Re-run Automation. 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 stop at the same time?
Why did every automation in the workspace stop at the same time?
The workspace reached its monthly automation action limit. Administrators are notified at 90 percent and 100 percent of the limit; automations resume at the monthly reset, or at once if the auto-billing toggle for extra runs is on. See Automation Limits.
Last verified 26 Oct 2026.