request.idempotency_conflict

The idempotency key was used for a different request


Type	`https://mthds.ai/errors/request.idempotency_conflict`
Family	`request`: The HTTP request itself, before any run.
Domain	`input`: the caller acts, by changing the request or its inputs
Retry	`no`: repeating the operation fails the same way
HTTP status	`409`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

An earlier request with the same idempotency key carried another body, so the runtime cannot treat this one as its repeat.

What to do

Generate a new idempotency key for every distinct request, and reuse a key only to repeat the very same request.

Next steps

A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the caller, and the second for any other reader.

Reader	Kind	Detail
The domain's actor	`change_input`	Send this request with a new idempotency key.
Any other reader	`change_input`	Pass this to the caller, who must send the request with a new idempotency key.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

The request's idempotency key was already used with a different body.

Parameters

This code declares no parameters, so its problems carry no params.