503 service_unavailable

Service unavailable. NoResponse could not start the assessment because of overload, a shutdown or a dependency that is down. An assessment that was started answers partial or pending instead of 503. The response carries Retry-After in whole seconds, from 1 to 3600.

What to do

Apply your fallback. Retry after Retry-After with the same Idempotency-Key, a bounded number of times. The SDKs do this for you.

Tip

This error is temporary. Retrying with the same Idempotency-Key is safe.

Example

{
  "type": "https://docs.noresponse.org/problems/service-unavailable",
  "title": "Service unavailable",
  "status": 503,
  "detail": "The assessment could not be admitted at all; retry after the Retry-After interval.",
  "code": "service_unavailable",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

Every error has this shape. See Errors and limits for the full list.