Request of the page failed

How to recognize it

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

HTTP/1.1 502
Content-Type: application/json

{
  "error": {
    "code": "request_failed",
    "message": "A request of the page that matches fail_if_request_failed failed (HTTP error status)."
  },
  "message": "A request of the page that matches fail_if_request_failed failed (HTTP error status)."
}

Common causes

• A script, stylesheet, image or API call of the page that answered 404 or 500, or did not load at all.
• A pattern that matches more than meant: a pattern matches the whole URL, and * stands for any characters.

How to fix it

1. Open the page with the browser’s developer tools (Network tab) and look for the failed request.
2. Narrow the pattern, for example https://cdn.example.com/* or *.css instead of *.
3. With diagnostics=true the error body adds the render’s diagnostics, with a link to a HAR file of the page’s requests.

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_request_failed, diagnostics. 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.