Automations are your ongoing moderation setups - and like anything that runs on its own, they occasionally need attention. This article covers everything you can do with an existing automation.
Where automations live
Go to Automations. Each automation shows its name, trigger, the rules it enforces, a results summary, when it was last triggered, and its status:
🔵 Active - the automation is on duty, watching for new content.
🟢 Processing… - it's currently checking newly arrived assets, with a count of how many are in progress.
🟠 Stopping… - it's finishing up after a stop was requested.
⏹️ Stopped - it was stopped and no longer processes anything.
❌ Failed / Pending - something went wrong, or the automation hasn't started yet.
Review an automation's results
Select Review assets to open the automation's results page.
It works exactly like a run's results page: status tabs, rule filter, Preview mode, manual approvals and rejections, and metadata saving. Results keep accumulating as long as the automation is active.
While an automation is processing, you can also narrow its results by date:
Use the All dates filter to focus on Today, Yesterday, the past 7/30/90 days, the past year, or a custom date range.
See an automation's configuration
Select Automation details in the row menu to open a side panel summarizing the automation:
Status and how many assets it has processed. For stopped automations, you'll also see when it was stopped.
Trigger & scope - the trigger (On upload, On tag change, or On metadata change) and what it watches: the asset type (Images or Videos), folders, tags, or metadata conditions.
Rules - every rule the automation enforces. Click a rule to see its details - if the rule was edited after the automation started, you'll see the version the automation actually uses.
If assets are waiting for a human decision, a callout shows "{count} assets are waiting for review" with a Review button that takes you straight to them.
Rename and share
From the row menu: Rename the automation, or Copy job URL to share it with a teammate.
Tip: Keep automation names descriptive ("On-upload checks - /user-submissions") so their purpose is obvious months later.
Stop an automation
Open the row menu and select Stop (available while the automation is processing).
If assets are still waiting to be processed, choose how to finish:
Finish queued assets, then stop - everything already in the queue gets moderated, then the automation ends.
Stop immediately - skip queued assets - the automation ends now; skipped assets won't be moderated.
Confirm with Stop Automation. While it finishes up, the automation shows Stopping…. Need it to end sooner? Select Stop again while it's stopping to skip the remaining queued assets.
Stopping is permanent - a stopped automation can't be turned back on. It keeps its results, though - you can still review them. To run the same setup again, use Restart.
Restart a stopped automation
Click Restart on a stopped automation to run the same setup again:
The ongoing moderation wizard opens prefilled with the original automation's trigger, scope, and rules - review each step and click Create Automation.
Restarting creates a new automation. The original stays in your list with its results.
If something from the original setup no longer exists (for example, a deleted rule or metadata field), the wizard warns you so you can adjust the configuration before confirming.
Change what an automation enforces
Automations keep the rules they were started with, so to change the standard, edit the rules themselves:
Editing a policy doesn't affect running automations - they keep the rules they were started with. Only editing one of those rules does.
When you save changes to a rule used by running automations, you choose: Restart the automation so it uses the updated rule (the default), or Keep the automation running the previous version - your changes are saved to the rule, but the automation doesn't use them. See "Edit, deactivate, or delete a rule".
Restarted automations process only new assets going forward - assets already queued finish processing before each automation stops, and assets that were already checked aren't re-moderated.
Deleting a rule or policy that an automation depends on stops and restarts the automation without it; if nothing would remain to moderate, the automation is stopped permanently.
Tip: After you restart automations with an updated rule, check that they're back to Active.
To change an automation's scope or trigger (different folder, different trigger), set up a new automation with the new configuration and stop the old one.
Delete an automation
Delete in the row menu removes the automation and its results from the list. You'll be asked to confirm with Delete Automation. If the automation is still active, deleting it also stops it - new assets won't be moderated, and a stopped automation can't be turned back on. Metadata saved to assets stays on the assets even if you later delete the automation.