idempotency-scope-missing

Status 500. The type of this problem is the address of this page.

What happened

The request carried an Idempotency-Key, and the server found nobody it could keep the key for: no signed-in user, and no resolver of its own that knows the caller. The package keeps the keys of each client apart and does not guess one from an address, because clients behind the same proxy would then see each other's answers.

What to do

This is a gap in the server's setup, not in the request, and the server has reported it. Its operators bind a ResolvesIdempotencyScope that knows the callers of the route, as the idempotency guide shows.