AI fix: path refused
type | https://docs.frem.sh/reference/api/errors/autofix-path-refused |
| HTTP status | 422 Unprocessable Content |
What it means
Returned by POST /orgs/{org}/code-security/sast/findings/{id}/autofix (AI fixes for SAST findings). No fix was requested and no AI model was called.
Since 2026-10-14 the same refusal is answered with the type ai-fix-path-refused from POST /orgs/{org}/code-security/sast/findings/{id}/ai-fix. The paths above are deprecated and keep answering autofix-path-refused until 2027-10-15. Branch on either type.
Example detail message returned with this error:
- The finding is in a test, CI, suppression or dependency file, which AI fix never changes.
The response also carries "reason": "path_refused".
What to do
Fix the finding by hand. AI fix never changes tests, CI configuration, CODEOWNERS, suppression files or dependency manifests.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/autofix-path-refused",
"title": "Unprocessable Content",
"status": 422,
"detail": "...",
"reason": "path_refused"
}Branch on type, not on title or detail - those are human-readable and may be reworded.