409 policy_version_conflict - NoResponse docs

{
  "type": "https://docs.noresponse.org/problems/policy-version-conflict",
  "title": "Policy version changed",
  "status": 409,
  "detail": "The configuration changed since it was read. Read the current settings and decide whether to retry with their policy_version.",
  "code": "policy_version_conflict",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

{
  "type": "https://docs.noresponse.org/problems/policy-version-conflict",
  "title": "Policy version changed",
  "status": 409,
  "detail": "The configuration changed since it was read. Read the current settings and decide whether to retry with their policy_version.",
  "code": "policy_version_conflict",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

HTTP 409 Not retryable

What to do

Read the current settings and compare the intervening changes. Submit a new change only after reviewing the newer policy.

In the SDKs

The Node and Python SDKs raise ConflictError. The Go SDK returns *apierrors.ConflictError, which you match with errors.As.

{
  "type": "https://docs.noresponse.org/problems/policy-version-conflict",
  "title": "Policy version changed",
  "status": 409,
  "detail": "The configuration changed since it was read. Read the current settings and decide whether to retry with their policy_version.",
  "code": "policy_version_conflict",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

Every error has this shape. Errors and limits lists every code.