An automation that did not run has one of five causes. The workspace reached its monthly action limit, the toggle is off, a step failed, the record already matched the trigger, or a field or connection the action needs is gone. Work through the five checks in order; most stopped automations are the first or the second.

You need the Administrator role, or the Solution Manager role for the solution, to open History and change the automation. If you have neither, send this page and the record name to the person who manages the solution.

Symptom: every automation in the workspace stopped at the same time, and Administrators received a usage notification.

Cause: every action in a run counts toward the monthly allowance (an automation with 5 actions spends 5 per run). At 90 percent Administrators receive an email, a SmartSuite notification and a usage popup in the Automations panel; at 100 percent automations are paused.

Fix: an Administrator opens Workspace Administration > Usage to see the actions used against the allowance. Turn on the auto-billing toggle there to add 1,000-action blocks at $15 and resume at once, or wait for the monthly reset. Unused add-on blocks expire at the end of the month; the allowances are in Automation Limits.

Symptom: one automation never runs and its History is empty.

Cause: the toggle to the right of the automation name is off. An inactive automation still counts toward the 50 automations per solution but does nothing.

Fix: open Automations from the Solution Menu, open the automation and set the toggle to the green ON state. From then on, every record that newly meets the trigger starts a run.

Symptom: History lists the run with an error status. Administrators and the Solution Managers of the solution also receive an email and a notification for each failed run.

Cause: one action could not complete. The run names the step and the error. Common ones are Unable to find choice, when the value is not an option in the Select field, and Usage Limit Reached. Missing record ID in inputs means an Update Records step points at a record that is not the trigger record.

Fix: open the automation, select History, open the failed run and read the step and its error. Fix the cause, then select Re-run Automation on that run. The full list of errors and fixes is in Common Automation Error Troubleshooting.

Symptom: the toggle is on, History shows no run, and the record met the condition before you switched the automation on.

Cause: When a record matches a condition fires only when a record changes from not matching to matching while the automation is on. Records that already matched do not fire it, and a formula field that changes on its own, such as WEEKDAY(TODAY()), does not count as a change.

Fix: save a change that makes the condition become true for that record, for example set the status to another value and back. For a daily job, use the At a scheduled time trigger instead of a formula. The trigger rules are in Automation Triggers.

Symptom: an automation that worked before now fails, and the run shows Field is Missing, Input is Missing or Insufficient Authentication Scopes.

Cause: a field an action writes was deleted or its option values changed, or a Gmail, Outlook or Google connection no longer has all the permissions it needs.

Fix: replace or remove the deleted field in the action, or update the value to the current option. For an integration, re-authenticate it with every permission box checked, then trigger a fresh run; a retry of the old run keeps the old credential.

Contact support when the five checks pass and History still shows no run or an error you cannot explain. 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 link to the automation (open it, select the three-dot menu and choose Copy Link). Add the start time of the run, or the time it should have run, and the name of the record.

Last verified 26 Oct 2026.