policy_version: The policy version is not the next one
A scope's documents are numbered 1, 2, 3 and so on; each new document is the current version plus one. Sending the current version again is allowed only with the same document (it brings any copy left a version behind up to date); the same version with a different document is refused. It also answers a document sent while another request changed the same scope; retry it. Nothing changed.
What to do
- A policy document is the scope's next version (current + 1); read GET /owner/v1/policies and resubmit.
On the wire
HTTP 409, error type state_error. Without Dynamo-Error-Detail: 1 every client receives {"error": "state", "reason": "policy_version", "detail": "…"} with no errorDetail: the policy routes add it only when the request sends that header, on a single-tenant core and on the hosted tier alike.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"reason": "policy_version",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "policy_version",
"message": "…",
"param": "policy",
"doc_url": "…/errors/policy_version.md",
"fix": "a policy document is the scope's next version (current + 1); read GET /owner/v1/policies and resubmit"
}
}
See policies and all error codes.