FurniOpsDocs
Error codes

overloaded

503 Server busy, retry later

HTTP status
503
Title
Server busy, retry later
Code
overloaded

What it means

The server is shedding load: under pressure it refuses the lowest-priority requests first (starting bulk exports, then expensive work and new streams, then reads on the standard tier) so that the rest keep being served. Other writes are never shed.

What to do

Wait the Retry-After it sends (2 to 10 seconds), then retry with backoff and jitter.

Example

Errors are RFC 9457 problem details, sent as application/problem+json. See Errors for every field.

{
  "type": "https://docs.furniops.com/errors/overloaded",
  "title": "Server busy, retry later",
  "status": 503,
  "code": "overloaded",
  "detail": "An explanation of this occurrence.",
  "request_id": "req_…",
  "doc_url": "https://docs.furniops.com/errors/overloaded"
}

Operations that answer it

  • GET /v1/agent/tools
  • GET /v1/agents
  • GET /v1/agreement-acceptances
  • GET /v1/agreements/{kind}
  • GET /v1/assistant/conversations
  • GET /v1/assistant/conversations/{conversation}
  • POST /v1/assistant/conversations/{conversation}/turns
  • GET /v1/assistant/me
  • GET /v1/assistant/memories
  • GET /v1/assistant/settings
  • GET /v1/assistant/spend
  • GET /v1/audit-events
  • GET /v1/billing
  • GET /v1/billing/credits
  • GET /v1/billing/credits/entries
  • GET /v1/billing/credits/purchases
  • GET /v1/billing/credits/purchases/{purchase}
  • GET /v1/billing/credits/rates
  • GET /v1/billing/invoices
  • GET /v1/brand
  • GET /v1/brand/claims
  • GET /v1/brand/claims/{id}
  • POST /v1/brand/claims/{id}/check
  • GET /v1/catalogue
  • GET /v1/catalogue/images
  • GET /v1/catalogue/publication-runs
  • GET /v1/catalogue/publication-runs/{id}
  • POST /v1/catalogue/publish
  • GET /v1/catalogue/variants
  • POST /v1/catalogue/withdraw
  • GET /v1/categories
  • GET /v1/changes
  • GET /v1/changes/recent
  • GET /v1/exports
  • POST /v1/exports
  • GET /v1/exports/{id}
  • GET /v1/mappings/{id}
  • POST /v1/mappings/{id}/confirm
  • GET /v1/match-pairs
  • GET /v1/match-pairs/{id}
  • GET /v1/matching/judge-settings
  • GET /v1/me/orgs
  • GET /v1/media/{id}
  • GET /v1/merges
  • GET /v1/merges/{id}
  • GET /v1/offers
  • GET /v1/org
  • GET /v1/plans
  • GET /v1/products
  • GET /v1/products/{id}
  • GET /v1/proposals
  • GET /v1/proposals/{id}
  • GET /v1/request-logs
  • GET /v1/request-logs/{id}
  • GET /v1/runs/{id}
  • GET /v1/source-probes
  • POST /v1/source-probes
  • GET /v1/source-probes/{id}
  • GET /v1/sources
  • GET /v1/sources/{id}
  • GET /v1/sources/{id}/categories
  • POST /v1/sources/{id}/categories
  • GET /v1/sources/{id}/inbound-messages
  • GET /v1/sources/{id}/mappings
  • POST /v1/sources/{id}/records
  • POST /v1/sources/{id}/replay
  • GET /v1/sources/{id}/runs
  • POST /v1/sources/{id}/runs
  • POST /v1/sources/{id}/test
  • GET /v1/status
  • GET /v1/status/history
  • GET /v1/stream
  • GET /v1/uploads/{id}
  • POST /v1/uploads/{id}/complete
  • GET /v1/usage
  • GET /v1/usage/series
  • POST /v1/variants/{id}/checks
  • GET /v1/vendor-profiles
  • GET /v1/vendor-profiles/{id}
  • GET /v1/vendor/stats
  • GET /v1/vendor/stats/products
  • GET /v1/vendor/stats/series
  • GET /v1/webhook-endpoints
  • GET /v1/webhook-endpoints/{id}
  • GET /v1/webhook-endpoints/{id}/deliveries
  • GET /v1/webhook-endpoints/{id}/deliveries/{delivery}