{% extends "_layout.html" %} {% set title = "Idempotency key reused with a different request" %} {% set status = "422 Unprocessable Content" %} {% set description = "The same Idempotency-Key with a different request." %} {% block main %}

You sent an Idempotency-Key this server has already seen, with a request that differs from the one it was first used for. A key replays exactly one request.

What to do

  1. Use a fresh key for a new request.
  2. When retrying after a timeout, resend the identical request with the same key — that is what the key is for.

The body

{
  "type":     "https://sc.example.com/server-errors/idempotency-key-reuse",
  "title":    "Idempotency key reused with a different request",
  "status":   422,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}

detail is prose and may be reworded at any time. Branch on type — never parse detail.

Where it comes from

POST /v1/jobs The same key with a different body.
POST /v1/jobs/{id}/submit The same key on a different job, or with a body that differs from the recorded submit body. The replay is scoped to the caller, the job and the request: it replays only when the path’s job id and the recorded submit body both match.
{% include "_help.html" %}

What this is not

job-state-conflict is a job already past the point where that call makes sense.

{% endblock %}