CONTENT_REJECTED

The site was not published.

What happened

The automatic content check stopped the publish. A house rule (a fixable technical rule) comes with its rule, path, line and fix in filter.reasons; a judgement call names only a content-policy category; the category checks_unavailable means the check itself couldn't finish and nothing was judged.

Fix

House rule: apply the fix and deploy again with the same deploy_id. checks_unavailable (retryable): call again with the same deploy_id after error.retry_after_seconds. Judgement call: don't reword, split or disguise the content to get past the check.

What to tell the user

For a judgement call: the site wasn't published because it may break the content policy, and they can appeal at support@carnival.dev with the request_id.

Agent hint

The exact error.hint text; Carnival fills each <…> for the call.

House rule:

The site breaks a Carnival house rule. Apply the fix in filter.reasons and deploy again with the same deploy_id.

Judgement call (category in place of <category>):

Not published: the site may break the content policy (<category>). Don't work around the check; the user can appeal at support@carnival.dev with the request_id.

checks_unavailable:

Carnival could not finish checking the site, so it was not published. Nothing needs to change: call carnival_deploy again with the same deploy_id in about 60 seconds.

All error codes: error codes

This page as Markdown