Automations run until something stops them. Some changes to rules and policies restart an automation automatically, and a few stop it for good. This article explains each case and what you'll see on the Automations page.
When to use this
An automation you didn't stop shows ⏹️ Stopped.
You see two automations with the same name.
An automation stopped moderating new uploads.
What restarts an automation
These actions replace a running automation with a new one. Each time, a dialog lists the affected automations before you confirm:
Saving a rule it uses, when you choose Restart the automation so it uses the updated rule.
Deactivating a rule it uses - the automation is restarted without that rule.
Deleting a rule it uses - the automation is restarted without that rule.
Deleting a policy it was started with - the automation is restarted without that policy.
What a restart looks like
The original automation stops. Assets already in its queue finish first, and meanwhile it shows 🟠 Stopping….
The original stays on the Automations page as ⏹️ Stopped, with all its results.
A new automation with the same name, trigger, and scope starts as 🔵 Active, with the updated set of rules.
The new automation moderates only assets that arrive from now on. Assets that were already checked aren't checked again, and existing results don't change.
Good to know: two automations with the same name usually mean a restart happened. The Active one is doing the work now; the Stopped one keeps the earlier results.
What stops an automation for good
You stopped it - with Stop in the row menu, then Finish queued assets, then stop or Stop immediately - skip queued assets.
Nothing would be left to moderate - deleting or deactivating the last rule an automation uses (or deleting the only policy it was started with) stops it instead of restarting it. The app tells you the automation was stopped because no moderation criteria remained.
You deleted it - deleting an active automation also stops it.
Stopping is permanent - a stopped automation can't be turned back on.
Run a stopped automation again
Click Restart on the stopped automation. The ongoing moderation wizard opens prefilled with its trigger, scope, and rules - review each step and click Create Automation. This creates a new automation; the original stays in the list with its results. If something from the original setup no longer exists, such as a deleted rule or metadata field, the wizard warns you so you can adjust it first.
What doesn't stop or restart it
Editing a policy - automations keep the rules they were started with.
Saving a rule and choosing Keep the automation running the previous version - the automation keeps going with the version it was running.
Editing a rule the automation doesn't use.
If a restart didn't go through
If the app says some automations could not be restarted and need attention, the original automation was stopped but the new one wasn't created. Find the stopped automation on the Automations page and click Restart to set it up again. A restart also can't start if one of its rules uses a rule type your account can't use anymore - remove that rule in the wizard before confirming. See "I can't find or use a rule type".
For everything else you can do with an automation, see "Manage your automations".