The review returned no findings
An empty result can be valid
Confirm that the intended files and hunks are present, the language is correct, and any essential context was supplied. Then continue normal testing and human review even if the result remains empty.
The diff is invalid or too large
Inspect the generated text before changing review options or retrying.
- Regenerate with git diff --unified=3 and confirm file plus hunk headers are present.
- Use jq -Rs or an equivalent serializer so JSON preserves newlines and escaping.
- Narrow the change or context when the response reports a 256,000-byte diff or 64,000-byte context limit.
Access and service errors
Use the HTTP status, structured error code, and requestId together.
- For 401, reconnect OAuth or obtain a fresh approved REST access token.
- For 403 or 404, verify the organization, membership, and provisioned product access without probing other identifiers.
- For repeated 429 or 5xx responses, stop automatic retries and contact support with requestId only.