PageCapture
Start free
Use casesGuidesDocsPlaygroundPricingLog in

matched_failed_request

A request made by the page failed and the failure policy rejected the capture.

target networkHTTP 500terminalnever billed

Common causes

  • · A subresource matching `fail_if_request_failed` did not complete.
  • · The pattern is broader than intended — matching is a case-insensitive substring, not a glob.
  • · A blocking rule (`block_ads`, `block_trackers`, `block_requests`) cancelled the very request the policy requires.

What to do

  • · Narrow the pattern to the resource that actually matters, such as the font or chart bundle.
  • · Check whether your own blocking rules cancel it before the policy sees it — one option can trip the other.
  • · Drop the policy when a missing subresource still produces an acceptable artifact.

Response shape

HTTP 500
{
  "is_successful": false,
  "error_code": "matched_failed_request",
  "error_message": "A request made by the page failed and the failure policy rejected the capture.",
  "documentation_url": "https://api.pagecapture.dev/docs/errors/matched_failed_request",
  "request_id": "req_01..."
}