provider_unavailable
provider_unavailable
Section titled “provider_unavailable”HTTP status: 502 Bad Gateway
How to fix
Section titled “How to fix”- Retry with exponential backoff. Start at 5 seconds, double on each retry, cap at 5 minutes. Provider outages typically clear within 10-15 minutes.
- Check the provider's status page (Bright Data / Oxylabs / Nimble Way / Zyte / Decodo) — see Providers for current vendor links.
- Configure workflow fallback so jobs cascade to a backup provider when the primary fails. Add a
servicenode with a fallback edge to a secondary provider'sservicenode in your workflow. - For sustained outages, pause the affected workflow via Workflows → Toggle rather than letting jobs pile up in the queue.
What this means
Section titled “What this means”We dispatched the request to a third-party scraping provider (Bright Data, Oxylabs, Nimble Way, Zyte, Decodo) and the provider returned a 5xx, timed out, or refused the connection. This is upstream — our infrastructure is fine. This is distinct from internal_error (our bug) and service_unavailable (our infrastructure outage).
Related errors
Section titled “Related errors”internal_error— our bug, not the provider'sservice_unavailable— our infrastructure briefly downquota_exceeded— your provider account hit its own per-account cap
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll surface which provider failed and what the upstream returned.