Skip to support content

Capture quality

Understand stealth capture errors

Read the error code to separate a target block from service or proxy availability.

Identify the error

  • TARGET_BLOCKED: the site still served a block or challenge.
  • STEALTH_CAPTURE_FAILED: another capture failure; inspect its recorded reason.
  • STEALTH_UNAVAILABLE: the stealth infrastructure is unavailable. A proxy authentication rejection (HTTP 407) is one possible cause.
  • SERVICE_BUSY: no capture worker was available; retry with a delay.

Choose a next step

Check service status and use a limited retry policy for availability problems. Confirm your plan includes stealth mode if the error concerns capability access. A normal capture of a simple public page can help establish whether the problem is limited to stealth or to one website.

Contact support with diagnostics

Include the request ID, URL, UTC timestamp, error code, and capture options. A proxy authentication failure is a service configuration problem rather than evidence that your screenshot API key is invalid. You do not need to provide proxy credentials to support.

Documentation

Related support articles

Need help with this issue?

Email support with this article, your request or capture ID, and the result you expected. Remove credentials and private information first.

Email [email protected]
Back to support