Security fix: already proposed

What it means

Returned by POST /orgs/{org}/code-security/deps/findings/{id}/autofix and POST /orgs/{org}/code-security/sast/findings/{id}/autofix (Security fixes). No pull request was requested.

Since 2026-10-14 the same refusal is answered with the type security-fix-already-proposed from POST /orgs/{org}/dependency-updates/security-fixes/requests and with the type ai-fix-already-proposed from POST /orgs/{org}/code-security/sast/findings/{id}/ai-fix. The paths above are deprecated and keep answering autofix-already-proposed until 2027-10-15. Branch on either type.

Example detail message returned with this error:

• A fix for this package in this repository is already queued or open.

The response also carries "reason": "already_proposed".

What to do

Use existing.pr_url in the response, or merge or close that pull request first.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/autofix-already-proposed",
  "title": "Conflict",
  "status": 409,
  "detail": "...",
  "reason": "already_proposed"
}

Branch on type, not on title or detail - those are human-readable and may be reworded.