Check the destination
Use a publicly reachable HTTP or HTTPS endpoint. Private, loopback, link-local, and metadata addresses are rejected. Check your endpoint’s access restrictions and certificate configuration. A URL that works only on your laptop is not reachable by the webhook service.
Check your receiver
- Confirm the receiver accepts the documented HTTP method and JSON payload.
- Inspect its request logs and response status at the time of delivery.
- Verify any configured webhook-secret handling against the API reference.
- Make processing idempotent so a repeated notification does not repeat downstream work.
Keep capture and delivery identifiers
Include the job or schedule ID, UTC timestamp, destination hostname, and the receiver’s HTTP status when contacting support. Redact webhook secrets and access tokens. For async jobs, you can also check status and retrieve a completed result through the API.
Documentation
Related support articles
Troubleshoot a scheduled capture
Check whether the schedule is active, its timezone, and the latest capture outcome.
Set up and review visual tests
Understand checkpoints, baselines, environment settings, and comparison results.
Use URLs and paths in a visual test journey
Navigate across public websites or reuse a base URL for relative paths.
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]