Preview deployments stuck in UNKNOWN/BLOCKED state before build starts

Help
1

Title:
Preview deployments stuck in UNKNOWN/BLOCKED state before build starts

Body:
Hello,

I am experiencing an issue with my Vercel project where all new Preview Deployments remain stuck in UNKNOWN/BLOCKED state before the build starts.

Project:
unwanalater/unwanalatrdigitalplatform-qq3e

Project ID:
prj_59feIkoHSfrcGLS2itfRpvPqs8Jz

Team ID:
team_SPMbRXzAnKsyUF2CHBn3DBN5

Git repository:
najeebhtamy3w-dev/unwanalatrdigitalplatform

Current Production Deployment:
unwanalatrdigitalplatform-qq3e-ge1nzixhh-unwanalater.vercel.app
Status: Ready

Symptoms:

  • New Preview Deployments show status UNKNOWN
  • No build duration
  • No build logs
  • Some deployment records return 404/not_found
  • Manual CLI deployment returns:
    • fetch failed
    • Upload aborted
    • This operation was aborted
    • Not authorized

What I already verified:

  • GitHub integration is connected correctly
  • I disconnected and reconnected the Git repository
  • Require Verified Commits is disabled
  • Environment variables are configured
  • vercel pull --environment=preview succeeds
  • vercel build succeeds completely
  • .vercel/output is generated successfully
  • Production remains healthy
  • New Git-triggered Preview Deployments still remain UNKNOWN/BLOCKED

Recent affected deployment IDs:
dpl_E811V8CA9UtpELkRpzDw5fy7qaW1
dpl_D2UCa4pdg2bHrNQ8NwLUNwRhAzjh

Recent affected preview aliases:
kfbhiblku
9tfclkn0k
ljhrgijf4
eb40t3g6f
d547k9hl7
qvpuuqiyz
pnsjinach

Vercel Support AI indicated that the deployments are stuck in a BLOCKED state in the platform pipeline.

Has anyone experienced this before, or can a Vercel team member help inspect the project deployment pipeline?

Thank you.

2

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

3

Thanks for sharing the deployment IDs. It looks like a git metadata configuration issue from what I can see in the logs.

Can you check that your email address for local commits matches your GitHub account? You can use git config user.email to check it and git config --global user.email <your-email-address> to update it if needed.