AI fix: not curated
type | https://docs.frem.sh/reference/api/errors/autofix-not-curated |
| 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-not-curated from POST /orgs/{org}/code-security/sast/findings/{id}/ai-fix. The paths above are deprecated and keep answering autofix-not-curated until 2027-10-15. Branch on either type.
Example detail message returned with this error:
- This rule is not on the AI fix list of rules with a narrow, checkable fix, so no AI fix is proposed for it.
The response also carries "reason": "not_curated".
What to do
Fix the finding by hand, or dismiss it with a reason. The rules AI fix covers are listed on the AI fix page.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/autofix-not-curated",
"title": "Unprocessable Content",
"status": 422,
"detail": "...",
"reason": "not_curated"
}Branch on type, not on title or detail - those are human-readable and may be reworded.