[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # Merging is blocked - Missing successful active Preview deployment 502 views · 8 likes · 22 posts Pavel Zbytovský (@zbycz) · 2024-08-03 · ♥ 2 Hi, i often get this message, although everything appears as successful. Any idea what do please?  My branch protection rules are as follows:  Pauline P. Narvas (@pawlean) · 2024-08-05 · ♥ 1 Hi, @zbycz! A few things to try: * Check with the project's configuration on GitHub, and take a look at the repo's merge settings * You may need to update branch protection rules on GitHub to remove unneeded checks * Does this only happen to specific projects? Or all of them? * A good old-fashioned re-installation of the [Vercel GitHub integration](https://vercel.com/docs/workflow-collaboration/comments/integrations#git-provider-integration)? Pavel Zbytovský (@zbycz) · 2024-08-06 · ♥ 1 Thanks, it happens only from time to time in one specific project. When I push another commit, it usually works. Lets close it now, i will write if it happens again :slight_smile: Pavel Zbytovský (@zbycz) · 2025-06-20 Hi, this has happened to me again several times. Usually with a user pushing to a fork. I think it may be relevant by having an old "master" branch. This particular PR is also having old base branch - but Github is showing `Merging is blocked Missing successful active Preview deployment.` and nothing about the branch. Could it be some Github bug? [https://github.com/zbycz/osmapp/pull/1110](https://github.com/zbycz/osmapp/pull/1110) I will leave to PR open for some time for possible investigation. //edit somebody else is having the same [issue](https://community.vercel.com/t/merging-is-blocked-missing-successful-active-deployments/11856/3) Pavel Zbytovský (@zbycz) · 2025-06-20 · ♥ 1 I am having the same issue [again](https://community.vercel.com/t/merging-is-blocked-missing-successful-active-preview-deployment/424) - possibly caused by old master branch. Pushing another commit usually fixes that, but it is very annoying. Pavel Zbytovský (@zbycz) · 2025-06-24 @pawlean 🙏 .. should i wait with the merging of that PR? Or it is not needed for debugging? Pavel Zbytovský (@zbycz) · 2025-07-08 @anshumanb - could you perhaps look into that? :folded_hands: thanks I left the PR still unmerged. Anshuman Bhardwaj (@anshumanb) · 2025-07-08 Hi @pavelzetradex, let me check what could be the issue. Anshuman Bhardwaj (@anshumanb) · 2025-07-08 Hi @zoan37, welcome to the Vercel Community! Sorry for the late reply. Is it happening on all the PRs? Does it also happen on other GitHub repos as well? Can you share the latest PR where this happened? @zbycz can you also answer these questions? Pavel Zbytovský (@zbycz) · 2025-07-08 · ♥ 1 Thanks for looking into it. This happens only very seldom - the PR https://github.com/zbycz/osmapp/pull/1110 is the last one. If it happens and somebody pushes another commit, it is fixed. I suspect, that it only happens when a non-contributor create a PR from their fork, and than the master branch gots some new commits. It happpens only on this repo (i dont have vercel anywhere else). Anshuman Bhardwaj (@anshumanb) · 2025-07-09 Thanks for sharing additional information @pavelzetradex. The PR you shared seems to be working now, as you said. Let me share your analysis with our team to see if this is a know issue or edge case. Pavel Zbytovský (@zbycz) · 2025-07-09 Thanks @anshumanb - though not sure what you mean. The PR i shared above is broken exactly in the way described above. Maybe you meant the link is working? :slight_smile: Anshuman Bhardwaj (@anshumanb) · 2025-07-09 Oh, thanks for confirming. I got confused because I don't see the merge button, only that the checks passed. Pavel Zbytovský (@zbycz) · 2025-07-09 · ♥ 1 Good! I think only maintainers see the Merge button. This is the screen I see (not that vercel passed, but "Meging is blocked" is right below):  Anshuman Bhardwaj (@anshumanb) · 2025-07-10 Hi @zbycz, thanks for sharing this. I reached out to the team and I've got a question for you: Can you confirm if you're using this rule in your repo `settings/rules` ?  Can you also share the expanded "additional settings"? Pavel Zbytovský (@zbycz) · 2025-07-10 · ♥ 1 Thanks @anshumanb :+1: My branches/master/rules settings: Deployment to preview required:  And branch not required to be up-to-date:  Matanya (@matanya) · 2025-07-14 I'm having the same issue, any updates on a fix? Anshuman Bhardwaj (@anshumanb) · 2025-08-06 Hi @zbycz, we're inspecting the issue. Is the repo in questions a monorepo? @matanya can you share about your repository as well (see the previous posts for details)? Pavel Zbytovský (@zbycz) · 2025-08-10 No, my repo is not a monorepo. Btw, the message [on the PR](https://github.com/zbycz/osmapp/pull/1110) changed - now it says there are merge conflicts. So i am going to resolve the PR.. it doesnt show anything useful now. Anyway, thanks for your help. 🙂 Lujo8089 (@lujo8089) · 2025-08-25 @anshumanb Thanks for looking in to this. We keep having the same issues here as well. Any update on a fix? We currently need to merge our PR:s from the command line. The frequency of this has ramped up, now it’s basically every PR. Anshuman Bhardwaj (@anshumanb) · 2025-08-26 Hi @lujo8089, welcome to the Vercel Community! I'm sorry that you are facing this issue. We weren't able to find a conclusive solution to this. Can you share the details about your repository settings and the PR if it's public? See the previous comments on this thread to find the instructions. Chris (@kikketer) · 2025-12-23 We are having a similar issue, the repository is a mono-repo and was working previous becoming a mono-repo. The path was that we had a mono-repo with a single Vercel project tied to it. Since then we have added a new Vercel project that’s using a different location in the mono-repo: `/apps` ` – application-a` ` – application-b` `/packages` ` – ....` Previously “a” was doing fine in the Github PRs, but now with “b” also doing it’s thing we are seeing a block in Github PRs even though everything is green.  And:  And: 
