- 00
- Features
- Auto Retry
Same provider, another attempt.
A recoverable failure is resubmitted to the same provider, on the next proxy in your list. Off until you turn it on.
Resilience
- Default
- Off
- Retries when on
- 2
- Most per provider
- 10
- Attempts per task, all providers
- 30
01Rule
Only failures a new attempt can clear.
- 01The attempt failsWith a code on the trigger list.
- 02Next proxyEach attempt moves to the next proxy in
task.proxy, wrapping around. - 03ResubmitUp to the limit. A request that was wrong, such as an invalid sitekey, ends on the first attempt.
- 04Out of retriesAuto Fallback takes over when it is on.
02Config
Turn it on per key or per request.
settings.retry, in POST /createTask
{
"settings": {
"retry": {
"enabled": true,
"maxRetries": 2,
"onErrors": [
"TASK_TIMEOUT",
"PROXY_BANNED"
],
"providerRules": {
"TwoCaptcha": {
"maxRetries": 1
}
}
}
}
}| Field | Range | Default |
|---|---|---|
| enabled | true, false | false |
| maxRetries | 0 to 10 | 2 |
| onErrors | Any trigger code | The 8 below |
| providerRules | Per provider: maxRetries, onErrors | None |
| settings.allowProxyReuse | true, false | false |
One proxy with retry on would reuse the same IP, so the request is rejected unless you pass more proxies or set allowProxyReuse.
03Triggers
8 codes retry by default.
Default retry triggers
- CAPTCHA_
UNSOLVABLE - TASK_
TIMEOUT - SERVICE_
UNAVAILABLE - PROVIDER_
UNREACHABLE - PROVIDER_
RATE_ LIMITED - PROXY_
CONNECTION_ FAILED - PROXY_
BANNED - ERROR_
PROVIDER_ ZERO_ BALANCE
04FAQ
Questions about Auto Retry.
01
Does retry switch providers?
No. Retry stays on the same provider. Moving to a different provider on failure is Auto Fallback.
02
Are validation errors retried?
No. Only refundable provider failures continue the chain. A bad request such as an invalid sitekey is terminal on the first attempt.