An asset came back ✅ Approved, but you expected it to be rejected or sent to review. The answer is usually in how the rule is set up, or in whether it ran on the asset at all. This article walks through the usual causes.
When to use this
An asset you consider off-brand or unsafe was approved.
A rule never seems to flag anything.
Start with the rule results
Select the asset and open the Details tab. Rule Results lists every rule that checked it, with the outcome, the confidence score, and an explanation. If the rule you expected isn't listed, it didn't run on this asset - see "The rule didn't run on the asset" below. For more on reading results, see "Why did my content get flagged?".
The rule is set the wrong way round
This is the most common cause. The rule finds what you asked about, but treats it as acceptable:
Pass on Yes / Pass on No - in rules that ask a yes/no question, this decides which answer passes. If your question describes something you don't want ("Does the video contain profanity?"), choose Pass on No.
Allowed content / Content to block - in Image Content Detection, choose Content to block when your question describes unwanted content.
Video Content Detection - read the What this rule checks summary on the rule. It says when the video fails. If it's the opposite of what you meant, rephrase the requirement and click Prepare rule again.
Defaults that allow something - for example, Text Detection has Allow text on objects on by default, so text printed on the product itself passes.
The rule isn't strict enough
Review threshold - Low decides more assets automatically. Choose Balanced or High, or set Custom thresholds, to send more borderline assets to review.
Settings for missing data - options such as Asset's metadata field is empty, No speech is detected in the asset's audio, or If no C2PA data is found decide what happens when the rule has nothing to check. If they're set to Approve, those assets pass.
A narrowed check - if a rule is limited to specific brands, other brands' logos aren't checked.
The rule didn't run on the asset
The rule is inactive. Inactive rules in a policy are skipped.
The asset wasn't in scope. Check the asset type (Images or Videos), the folder, and for automations, the trigger and what it watches. Automations moderate assets that arrive after they start, not earlier uploads.
The automation uses an earlier version of the rule. If you saved a change and chose Keep the automation running the previous version, the automation doesn't use your change. A clock icon on the rule's chip shows that a newer version exists.
The result is from before your change. Editing a rule doesn't re-check assets that were already moderated. Start a new one-time run on those assets to apply the updated rule.
Video-specific causes
Brief appearances - on-screen text rules check a set number of frames per second (Frames per second to sample, 1 by default). Text that's on screen for a moment can fall between frames - raise the rate to catch it.
Video Content Detection mode - in Advanced settings, Most frames only reacts when most frames match, while One frame is enough reacts to a single frame. Use the second for things that appear only briefly.
What to do next
Fix the asset's result yourself: Reject it, or Flag for Review.
Fix the rule, then test it with a small one-time run before relying on it. If running automations use the rule, choose Restart the automation so it uses the updated rule when you save - see "Edit, deactivate, or delete a rule".
If the rule shows Error instead of a result, see "Why does a rule show an error instead of a result?".