### Summary MRs created via CI/CD push options with `merge_request.merge_when_pipeline_succeeds` intermittently fail to auto-merge after the pipeline passes. The MR stays stuck in "Set to auto-merge" state for hours/days, but **merges within seconds of opening the MR page in a browser**, with no interaction beyond loading the page (i.e., without clicking on "Merge" manually). ### Steps to reproduce It's not easy to reproduce it because it happens intermittently, but I experience this a few times a week with my team, which is relatively small (~15 people) 1. From a CI/CD pipeline on GitLab.com, push a branch with auto-merge push options: ```bash git push --force \ -o merge_request.create \ -o merge_request.merge_when_pipeline_succeeds \ -o merge_request.target=master \ -o merge_request.title="Example Title" \ -o merge_request.remove_source_branch \ -u origin "auto/example" ``` 2. Wait for the MR pipeline to pass (status is green). 3. **Do not** open the MR page in a browser. 4. Observe the MR is **not merged** despite all merge checks passing (pipeline passed, no conflicts, no required approvals, no unresolved threads). 5. Open the MR page in a browser. 6. Observe the merge completes **immediately** after page loading — no clicks or interaction required. ### Example Project <!-- Unable to share the project, but this is reproducible on any project using the push options above. It happens intermittently — some MRs merge fine, others get stuck. --> ### What is the current *bug* behavior? After the pipeline succeeds, the MR remains stuck in "Set to auto-merge" state indefinitely. The merge only executes when the MR page is loaded in a browser. This is intermittent (a few times per week) and has been happening for approximately one year. ### What is the expected *correct* behavior? The MR should auto-merge server-side once the pipeline succeeds and all merge checks pass, without requiring any browser interaction. ### Relevant logs and/or screenshots Screencast showing an MR open for 15 hours with a passed pipeline, merging right after the page was opened (check the Activity section after page load). Some of the errors visible in the screencast are not always present when this happens if I remember correctly {width=900 height=507} ### Output of checks This bug happens on GitLab.com #### Results of GitLab environment info N/A — GitLab.com (SaaS) #### Results of GitLab application Check N/A — GitLab.com (SaaS) ### Possibly related issues There are several issues related to auto-merge failures, but this one seems to be a different case. - #389415 — Merge Request Auto-Merge Sometimes Gets Stuck - #336481 — Auto Merge using push options can intermittently fail - #275973 — MR failed to merge automatically when created by git push option - #424041 — Auto-merge doesn't merge after second commit