Neon Postgres integration provisioning failure blocking Vercel preview deployments

Help
, ,
1

Hi Vercel Community,

Our GitHub PR workflow is blocked only by the Vercel preview deployment check. All other checks are passing.

Project Details

  • Project: kimikimichineses-projects / esg-rdt-master
  • Repo: kimikimichinese-bot/ESG_RDT_Master
  • PR: #821
  • PR head SHA: c266bd0e1575bba9d8fb3686908f2913d0109276

Failing Vercel Check

vercel.com

1200×630 4.06 KB

[project] - Deployment Overview – Vercel

Current Behavior

  • Preview deployments fail BEFORE the build starts (Builds: . [0ms])
  • Vercel UI / vercel inspect shows:
    • readyStateReason: “Provisioning integrations failed”
    • errorMessage: “Resource provisioning failed”
  • This appears related to Neon Postgres integration provisioning for Preview.

Example Failing Preview Deployments

  1. https://esg-rdt-master-5f72it374-kimikimichineses-projects.vercel.app
    • Deployment ID: dpl_HidEPFchVbbK9E5zJmwoN9KimibX
    • Symptom: Builds . [0ms]
  2. https://esg-rdt-master-qdy04urp6-kimikimichineses-projects.vercel.app
    • Deployment ID: dpl_HbsLrPY4Zu6ipJ8fyGjownHnochS
    • Symptom: Builds . [0ms]

Production deploy succeeds (issue appears preview-only / integration provisioning).

Question

Has anyone encountered this Neon integration provisioning failure for Preview deployments? Any safe workaround to unblock preview deploys (e.g., disabling preview DB provisioning / using a fixed preview database connection) until Vercel resolves the integration provisioning?

Thanks!

5

Update / Resolution:

Root cause was Neon branch limit on the Free plan. We had 10/10 branches (mostly Vercel-created preview/* branches), so the Vercel Neon integration step “Create database branch for deployment” failed. That caused “Provisioning integrations failed / Resource provisioning failed” and builds that never started (0ms).

Fix:

  • Deleted old preview/* branches in Neon to free branch slots (went from 10/10 to 1/10).
  • Re-triggered the Vercel preview deployment (empty commit / redeploy).

Result:

  • Neon provisioning succeeded, build ran normally, deployment became Ready, and the GitHub “Vercel” check turned green.

Prevention:

  • Keep Neon branches below the plan limit (periodically delete old preview/* branches), or upgrade plan / disable per-preview DB branching if possible.