Guides
Retry Strategy
Build fault-tolerant job orchestration.
Guides
Build fault-tolerant job orchestration.
| Error Type | Retry? | Notes |
|---|---|---|
| 429 rate_limited | Yes | Backoff with jitter |
| 5xx server error | Yes | Retry 3-5 times |
| 4xx invalid_request | No | Fix payload first |
| insufficient_credits | No | Top up credits |
| Request Type | Max Retries | Backoff |
|---|---|---|
| Create/Start job | 3 | Exponential + jitter |
| Status polling | Unlimited until timeout window | Adaptive interval |
| Download/output fetch | 2-3 | Short linear or exponential |
Retry Strategy belongs to the Guides section and covers build fault-tolerant job orchestration.
The page is written for developers and operators who need predictable video background removal behavior in production, not just a one-off demo request.
Before you promote this workflow, test it with at least one short clip, one longer clip, and one visually difficult clip from your actual product or customer segment.
For support and debugging, persist the original input reference, selected model, output format, credit usage, and final job status alongside your internal user or project id.
| Question | Answer |
|---|---|
| Is Retry Strategy required for every integration? | Use it when the topic affects your setup, quality target, or operational workflow. |
| What should I test before going live? | Verify success, failure, timeout, retry, and insufficient-credit paths with realistic video files and the same output format you plan to ship. |
| How does this connect to the rest of the API? | Most workflows connect upload or source URL handling, job creation, status polling, output retrieval, usage tracking, and operational logging. |