Skip to main content

Why does a rule show an error instead of a result?

What a rule error means, the common causes, and how to get the asset checked

Sometimes a rule can't check an asset - the file can't be read, or the rule is missing something it needs. Instead of a pass, fail, or review outcome, the rule shows an error. This article explains what you'll see, the common causes, and how to get the asset checked.

What you'll see

  • In Table view, the rule's outcome reads Error. Hover over it to see the reason.

  • On the asset's card, a note such as 1 rule errored (or All rules errored).

  • In the asset's Details tab, Rule Results shows the rule with the reason it couldn't run.

An error never approves or rejects an asset on its own. The asset is sent to 🚩 Needs review - unless another rule rejected it, in which case it's ❌ Rejected.

Common causes

  • The file couldn't be read. The asset was deleted or replaced while the run was in progress, or the file is damaged or in a format the rule can't open. You'll see reasons such as "Failed to download image" or "Could not read image file".

  • The video is too long or too large. Rules that look at the frames check up to 600 frames per video - about 10 minutes at 1 frame per second - and files up to 500 MB. The reason names the limit, for example "Video file too large".

  • The asset is missing information the rule needs. Minimum DPI needs resolution data in the file ("Image has no resolution (DPI) metadata"). Metadata rules need the asset's structured metadata ("Structured metadata could not be loaded for this asset").

  • The rule's settings are incomplete or invalid. For example, "No allowed formats configured", "Invalid naming pattern", or a metadata question that doesn't reference a metadata field. This is most common with imported rules - edit the rule, complete its Configuration, and save it.

  • A temporary analysis problem. Reasons such as "Check failed unexpectedly" or "This check couldn't be completed. Please review manually." usually don't repeat on a new run.

An empty metadata field isn't an error. Metadata rules have their own setting for it, Asset's metadata field is empty, which decides whether those assets are approved, rejected, or sent to review.

What to do

  1. Open the asset and read the reason in Rule Results.

  2. Fix the cause if you can - complete the rule's settings, replace the file, or shorten the video.

  3. Decide the asset yourself with Approve or Reject, or check it again with a new one-time run on just those assets. You can find them in the wizard by name or public ID - see "Search for assets with expressions".

  4. If the same error keeps appearing across many assets, contact support with the run's link (Copy URL in the row menu) and the rule's name.

For how to start a new run, see "Run one-time moderation".

Did this answer your question?