# Async API webhook retries, 410 for unavailable results, reference refresh > Source: https://scrape.do/documentation/changelog/2026-11-17-async-api-update/ 2026-11-17 ยท improvement ## Webhooks that return 404 or 410 When your webhook endpoint answers `404` or `410`, the Async API no longer burns through the normal retry ladder. The webhook gets one more attempt about an hour later, so an endpoint that is briefly gone during a redeploy still gets its results. If it still answers `404` or `410`, the webhook is marked `failed`. Other failures (timeouts, connection errors, `5xx`) are retried as before. The full delivery rules are now documented under [webhook delivery](/documentation/async-api/create-job#webhook-delivery). ## `410 Gone` on Get Task In rare cases a task still exists but its stored content can no longer be read. [Get Task](/documentation/async-api/get-task) now returns `410 Gone` with `Task response content is no longer available.` for these tasks. Retrying will not bring the content back, so create a new job for that URL. Results are still kept for 3 days after the job is created. ## Reference refresh The Async API reference now matches what the API actually returns and accepts: - Task responses list `WebhookURL`, `WebhookStatus`, `WebhookRequestTime` and `TraceID`. - The create-job schema documents the `Plugin` field, the 1000-target limit and the `Timeout` / `RetryTimeout` ranges. - List Jobs documents the `status`, `start_from`, `start_to` and `sort` query parameters in the API schema. Plugin jobs also gained new keys and stricter up-front validation. See the [plugin reference](/documentation/async-api/plugins) for details.