ERR::SCRAPE::SCENARIO_DEADLINE_OVERFLOW
Submitted scenario would require more than 30s to complete. See all errors
- Retryable: No
- HTTP status code: 422
If retryable is "yes" and retry=true
the errored is retried internally by scrapfly. In the end if you get the error, it means the errors happened 3 times or
the error happened after retries from other kind of retryable error in the last retry round.
Related Documentation
Read Error From Response Body
{
"config": { ... },
"context": { ... },
"result": {
[...],
"status": "DONE",
"success": false,
"reason": null,
"error": {
"http_code": 422,
"code": "ERR::SCRAPE::SCENARIO_DEADLINE_OVERFLOW",
"description": "ERR::SCRAPE::SCENARIO_DEADLINE_OVERFLOW",
"error_id": "9993a546-b899-4927-b788-04f5c4e473d5",
"message": "Useful hint with details about your error",
"scrape_id": "7c61352c-f1a7-4ea6-a0b8-198d7ac6fe1a",
"retryable": false,
"doc_url": "https://scrapfly.io/docs/scrape-api/error/ERR::SCRAPE::SCENARIO_DEADLINE_OVERFLOW"
},
[...],
}
}
Read Error From Response Headers
Moslty relevant with HEAD
request
- X-Scrapfly-Reject-Code:
ERR::SCRAPE::SCENARIO_DEADLINE_OVERFLOW
- X-Scrapfly-Reject-Description:
Submitted scenario would require more than 30s to complete
- X-Scrapfly-Reject-Doc:
https://scrapfly.io/docs/scrape-api/error/ERR::SCRAPE::SCENARIO_DEADLINE_OVERFLOW
- X-Scrapfly-Reject-Http-Code:
https://scrapfly.io/docs/scrape-api/error/422
- X-Scrapfly-Reject-Retryable:
false