409 group_conflict - NoResponse docs

{
  "type": "https://docs.noresponse.org/problems/group-conflict",
  "title": "Group state changed",
  "status": 409,
  "detail": "Read the group, screening or person before retrying. One screening of a group runs at a time, a finished screening cannot change, expected_version must be the group's current version, and a password or hash search runs only once it is counted.",
  "code": "group_conflict",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

{
  "type": "https://docs.noresponse.org/problems/group-conflict",
  "title": "Group state changed",
  "status": 409,
  "detail": "Read the group, screening or person before retrying. One screening of a group runs at a time, a finished screening cannot change, expected_version must be the group's current version, and a password or hash search runs only once it is counted.",
  "code": "group_conflict",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

HTTP 409 Not retryable

What to do

Read the group or its screenings. Wait for the running screening to finish or cancel it, or send the current version. Read the person and run the search once it is counted.

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/group-conflict",
  "title": "Group state changed",
  "status": 409,
  "detail": "Read the group, screening or person before retrying. One screening of a group runs at a time, a finished screening cannot change, expected_version must be the group's current version, and a password or hash search runs only once it is counted.",
  "code": "group_conflict",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

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