The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

https://vercel.com/docs/projects/domains/troubleshooting

You can also use v0 to narrow down the possibilities.

If I understood correctly: You can do this by assigning a custom domain to your staging branch and using Vercel’s promotion workflow with that domain.

First, set up a staging domain like staging.yourdomain.com and attach it to your staging branch in your project settings.

Once that’s done, turn off auto-assignment so new deployments on that branch don’t immediately take over the domain. That way nothing gets promoted until you choose to.

After your migrations finish, you can manually promote the exact deployment you want to serve on the staging domain either from the Vercel dashboard or by using the CLI.

The idea is to treat your staging branch the same way you treat production: give it its own domain, then promote deployments to that domain only when they're ready. Once that custom domain is tied to the branch, you get the same “build first, promote later” workflow that production uses.

If you prefer the CLI, you can promote a deployment with:

1
vercel promote <deployment-url> --scope=<team-slug>

This gives you two independent deployment pipelines: one for main → production domain, and another for staging → staging domain.

Hi @harrisonc-4086, just checking in to see if you were able to set up the staging branch with the promotion workflow you were looking for or if you still need assistance. Let me know how it's going!