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.
⏹️ 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.
Trigger & scope - the trigger (On upload, On tag change, or On metadata change) and what it watches: folders, tags, or metadata conditions.
Rules - every rule the automation enforces.
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, do not process queued assets - the automation ends now.
Confirm with Stop Moderation.
A stopped automation keeps its results - you can still review them.
Change what an automation enforces
Automations follow the rules and policies they were configured with, so to change the standard, edit the rule or policy itself:
When you save changes to a rule or policy used by running automations, the app lists the affected automations and asks to stop and restart them so your changes apply.
Restarted automations process only new assets going forward - they don't re-moderate assets that were already checked.
Deleting a rule or policy that an automation depends on follows the same pattern; if nothing would remain to moderate, the automation is stopped permanently.
Tip: After any rule or policy change, check that affected automations are 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. Stop it first if it's still processing. Metadata saved to assets stays on the assets even if you later delete the automation.