Skip to main content
Code: embeddings_provider_unknown_error HTTP status: 502 Type: server_error

​
When it fires

The upstream embedding model returned an error that the platform’s error-mapping table doesn’t yet recognize. This is a platform-side bug — engineering will add the mapping in the next release. Logged at ERROR so it surfaces in on-call dashboards. Any held credits are released; no row is committed.

​
How to fix it

Retry with exponential backoff — the failure is treated as transient until classified. Suggested schedule: 1s → 2s → 4s → 8s with jitter, up to ~30s total. If the error keeps recurring on the same request shape, open a support ticket with the response request_id so we can capture the upstream signal and pin the mapping. Identical inputs that consistently trigger an unmapped error are the most useful repro a customer can give — the mapping work is mechanical once we see one. Sending Idempotency-Key on a retry is safe: a successful retry will commit a new embedding row, and the cached entry for the failed key will be evicted on the next successful call with the same key.

​
Example response

{
  "error": {
    "type": "server_error",
    "code": "embeddings_provider_unknown_error",
    "message": "The embedding provider returned an unrecognized error. Engineering has been notified. Retry with backoff.",
    "param": null,
    "doc_url": "https://docs.aurous-labs.com/errors#embeddings_provider_unknown_error",
    "request_id": "req_01HXMQ7Z3K8Y2ABCDEFGHJKM"
  }
}