Deploy Hook issue with Multiple Vercel Environments on Same Branch

Hi there!

I recently configured a custom "staging" Vercel deployment environment that deploys from the same branch as the "production" environment (both targeting the main branch). We're triggering a deploy hook daily, but I noticed that since adding the custom environment, only the staging deployment is being built.

Is there a way to ensure that both environments are built? Or to specify which environment should be built via the deploy hook? Or to make the "production" build the one with highest priority when a hook with multiple environments attached gets called?

Thanks, Klaas

Hi, Klaas! Welcome to the Vercel Community

Thanks for reaching out about the deploy hook issue with multiple Vercel environments on the same branch. I appreciate you bringing this to our attention!

Here's what's happening:

Vercel has a specific behavior when it comes to multiple environments (like production and staging) pointing to the same branch. To prevent deployment conflicts, Vercel only allows automatic deployments for one environment per branch, typically the production environment . This is why you're experiencing issues with deploy hooks for your additional environments.

To resolve this, you have a few options:

Use separate branches for different environments (recommended): Create a 'staging' branch and point your staging environment to it. This way, both environments can have their own deploy hooks.
Implement a custom CI/CD pipeline: Use GitHub Actions or another CI tool to manage your deployments. You can set up a workflow that triggers the appropriate deploy hooks in the order you need.
Vercel's promotion workflow: Deploy to one environment first (e.g., staging) and then use Vercel's promotion feature to promote to other environments (e.g., production) . This allows you to maintain control over the deployment process.
Manual deployments for non-production environments: While not ideal for automation, you could manually trigger deployments for your staging environment using the Vercel dashboard or CLI.
Vercel Environments Overview: https://vercel.com/docs/concepts/projects/environment-variables#environments
Vercel Deployment Overview: https://vercel.com/docs/concepts/deployments/overview
Git Branch and Environment Relationship: https://vercel.com/docs/concepts/git/vercel-for-github#branch-organization
Creating and Managing Deploy Hooks: https://vercel.com/docs/concepts/deployments/deploy-hooks
Promoting Deployments (for environment promotion workflow): https://vercel.com/docs/concepts/deployments/promoting-deployments
Vercel CLI for Manual Deployments: https://vercel.com/docs/cli
Environment Variables and Secrets: https://vercel.com/docs/concepts/projects/environment-variables
Vercel for GitHub (or GitLab/Bitbucket) Integration: https://vercel.com/docs/concepts/git

Happy Christmas Eve

Hi Pauline, thanks for your reply!

Vercel only allows automatic deployments for one environment per branch, typically the production environment

Understood - but isn't it a bug that, in our case, the staging environment apparently takes precedence over the production environment?

(We've also enabled the "Prioritize Production Builds" but that doesn't seem to be related to this)

Hi Pauline - I just wanted to follow up on my latest question in case it got overlooked :-)

Thanks, Klaas

Another gentle reminder :) Is it perhaps better to reach out to Vercel support?

Hi , I believe I fixed the issue. Can you try the deploy hook again and let me know if it is working as expected? Thanks!

Hi Cody - You're right! As of this morning our daily deploy hook triggered the production build 🥳 (or actually it triggered both environments that build from the main branch - perfect!)

Thanks -- Klaas

Appreciate your patience with this! Let us know if we can help with anything else See you around the community

Hi there!

Thanks, Klaas

Hi, Klaas! Welcome to the Vercel Community

Thanks for reaching out about the deploy hook issue with multiple Vercel environments on the same branch. I appreciate you bringing this to our attention!

Here's what's happening:

To resolve this, you have a few options:

Use separate branches for different environments (recommended): Create a 'staging' branch and point your staging environment to it. This way, both environments can have their own deploy hooks.
Implement a custom CI/CD pipeline: Use GitHub Actions or another CI tool to manage your deployments. You can set up a workflow that triggers the appropriate deploy hooks in the order you need.
Vercel's promotion workflow: Deploy to one environment first (e.g., staging) and then use Vercel's promotion feature to promote to other environments (e.g., production) . This allows you to maintain control over the deployment process.
Manual deployments for non-production environments: While not ideal for automation, you could manually trigger deployments for your staging environment using the Vercel dashboard or CLI.
Vercel Environments Overview: https://vercel.com/docs/concepts/projects/environment-variables#environments
Vercel Deployment Overview: https://vercel.com/docs/concepts/deployments/overview
Git Branch and Environment Relationship: https://vercel.com/docs/concepts/git/vercel-for-github#branch-organization
Creating and Managing Deploy Hooks: https://vercel.com/docs/concepts/deployments/deploy-hooks
Promoting Deployments (for environment promotion workflow): https://vercel.com/docs/concepts/deployments/promoting-deployments
Vercel CLI for Manual Deployments: https://vercel.com/docs/cli
Environment Variables and Secrets: https://vercel.com/docs/concepts/projects/environment-variables
Vercel for GitHub (or GitLab/Bitbucket) Integration: https://vercel.com/docs/concepts/git

Happy Christmas Eve

Hi Pauline, thanks for your reply!

Vercel only allows automatic deployments for one environment per branch, typically the production environment

Understood - but isn't it a bug that, in our case, the staging environment apparently takes precedence over the production environment?

(We've also enabled the "Prioritize Production Builds" but that doesn't seem to be related to this)

Hi Pauline - I just wanted to follow up on my latest question in case it got overlooked :-)

Thanks, Klaas

Another gentle reminder :) Is it perhaps better to reach out to Vercel support?

Hi , I believe I fixed the issue. Can you try the deploy hook again and let me know if it is working as expected? Thanks!

Hi Cody - You're right! As of this morning our daily deploy hook triggered the production build 🥳 (or actually it triggered both environments that build from the main branch - perfect!)

Thanks -- Klaas

Appreciate your patience with this! Let us know if we can help with anything else See you around the community