content_missing_specified_string
The rendered page did not contain the required content.
target contentHTTP 500terminalnever billed
Common causes
- · `fail_if_content_missing` was set and the marker never appeared in the rendered text.
- · The content arrives after capture, so the policy evaluated an incomplete page.
- · The text exists in an iframe or shadow root, and the policy reads the main document body.
What to do
- · Pair the policy with `wait_for_selector` so the check runs after the content exists.
- · This is the policy doing its job: a page that rendered without the required content produced a wrong artifact, and failing costs you nothing.
- · Match on a short, stable string — the check is a plain substring of the body text, and it is case-sensitive.
Response shape
HTTP 500
{
"is_successful": false,
"error_code": "content_missing_specified_string",
"error_message": "The rendered page did not contain the required content.",
"documentation_url": "https://api.pagecapture.dev/docs/errors/content_missing_specified_string",
"request_id": "req_01..."
}