Content condition failed

How to recognize it

The API answers with status 422 and a JSON body with the message and the error.code content_condition_failed, for example:

HTTP/1.1 422
Content-Type: application/json

{
  "error": {
    "code": "content_condition_failed",
    "message": "The page contains a text of fail_if_content_contains."
  },
  "message": "The page contains a text of fail_if_content_contains."
}

Common causes

• fail_if_content_contains: the page shows one of the texts, such as Access denied or Out of stock.
• fail_if_content_missing (The page does not contain a text of fail_if_content_missing.): an expected text is not on the page, for example because it showed a login, a consent wall or an error instead.
• Content that appears only after the render captured the page.

How to fix it

1. Send the same request without the condition and with format=png to see what the page showed.
2. Wait for the content with wait_for_selector or wait_until before the conditions are checked.
3. Only the text the page shows counts. Case and white space do not matter, every other character does.

Billing

The first 25 failure conditions a day are free for each account (selector_not_found, content_condition_failed, request_failed and action_failed together, per UTC day). After that, each counts as one request, like a render. One exception: when an evaluate step of actions or the scripts ran in the page before the render failed, it is billed as one request, because that code could read the page, unless the failure is ours.

Related parameters

fail_if_content_contains, fail_if_content_missing, wait_for_selector. Each is described in the take endpoint reference.

Every response carries an X-Request-Id header. If this page does not explain the error, write to support@screenshotbase.com with that id. All statuses: status codes.