Autofix did not open a review request

Symptom

An Autofix or Improvement Job completed but did not open a pull request or merge request.

Quick checks

• Read the run outcome and provider links.
• Confirm Open a pull request with the fix was enabled for that job.
• Check whether an issue, existing PR/MR, or already-resolved result was recorded.
• Read verification and limitations before retrying.

Diagnose the outcome

Issue-only mode intentionally forbids file edits, branches, and review requests. In issue-plus-review-request mode, code is still conditional. The candidate may no longer apply to the default branch, be covered by an existing issue or review request, exceed safe scope, require a product or owner decision, or lack credible verification. Missing provider API access, invalid source context, or an ambiguous repository can also force a no-write outcome.

Some published improvement categories are currently guided prototypes and explicitly produce reports without code changes. Check the catalog page for current maturity.

Resolve the problem

If issue-only was accidental, update the job’s write behavior for future runs; do not expect the completed run to retroactively create a branch. Resolve duplicate or existing provider work directly. Repair the documented test or environment baseline when verification was the blocker. Rerun the source audit when the candidate context is stale.

Do not broaden scope or disable checks merely to force a PR/MR. High-blast-radius work should remain in the issue for qualified human implementation.

Escalate safely

Provide the repository, improvement name, run time, configured write behavior, outcome, issue or existing PR/MR links, and redacted verification summary. Do not send credentials, secret findings, or internal platform artifacts.