Neon Marketplace deployment action times out before builds start on two projects

Hi Vercel team and community,

We have a reproducible release blocker affecting PR #31. Two Vercel Preview deployments time out during Neon Marketplace integration provisioning before the application build starts.

Account and source

Vercel team: shengzeqiang888s-projects (Hobby)
GitHub repository: https://github.com/shengzeqiang888/jingye-assistant
Pull request: https://github.com/shengzeqiang888/jingye-assistant/pull/31
Branch: codex/app-store-release-hardening
Commit: fbc78b733c70aa82679c9eca270729c622ccbc21

Affected deployments

jingye-assistant: https://vercel.com/shengzeqiang888s-projects/jingye-assistant/9mm6H8N1JNXrcjt7VMQ7gT7jL2rK — failed after about 3m15s
jingye-assistant-staging: https://vercel.com/shengzeqiang888s-projects/jingye-assistant-staging/7UvLGo8g2uf4evjwydePaaGnuXQ2 — failed after about 3m51s

Observed behavior

Both deployments fail in Provisioning/Configuring Integrations.
The failing action is Neon: Create database branch for deployment.
The application build never starts and no build logs are produced.
This reproduced on automatic deployment, manual redeploy, and one post-cleanup redeploy for each project.

Neon resources

jingye-assistant-db — Neon project fragrant-hall-08272854
jingye-assistant-staging-db — Neon project quiet-mountain-99364667

Diagnostics already completed

The Vercel-created branch preview/codex/app-store-release-hardening exists in both Neon projects and was activated during the failed action.
Both projects were originally at 8/10 branches with compute and storage well below Free-plan limits.
We removed only the obsolete Preview branch for merged PR #27 from each project, reducing both to 7/10, then retried once. The same timeout remained, so branch capacity is not the cause.
GitHub CI passes.
Vercel and Neon dashboards show the integrations/resources as available, and public status pages report operational systems.
Vercel Support routes Marketplace cases to the integration owner. Neon Free support cannot open a private case, and Neon's current official Discord invitation is invalid.

This appears to be a Neon Marketplace deployment-action webhook/callback or Vercel resource-integration state problem: Neon partially completes the branch work, but the Vercel deployment action never completes.

Could a Vercel staff member or the Neon Marketplace integration owner inspect and repair the integration state for these two projects, or provide a safe recovery procedure? We have not disconnected resources, rotated secrets, disabled Preview database isolation, or modified production data.

No secrets, credentials, database connection strings, or business data are included in this report.

Hi — you helped get the underlying issue resolved in a nearly identical Neon integration branch-creation timeout: https://community.vercel.com/t/neon-integration-branch-creation-timeout-and-access-denied-errors-on-vercel/31392

Vercel Community

Neon integration branch creation timeout and access denied errors on Vercel

Hi everyone, We’ve been completely blocked for 48+ hours due to issues with the Neon integration. Symptoms: Branch creation times out (~2m49s) on every...

Could you please route this incident to the relevant Vercel/Marketplace engineers?

Quick lookup:

Team slug: shengzeqiang888s-projects
Main Vercel project: jingye-assistant — prj_WrCZulC2SEnI8CTpkUpINnmuSzHh
Staging Vercel project: jingye-assistant-staging — prj_VLxFIvgDJBXGXmRKC270sNC6Z2pA
Latest failed deployment IDs: 9mm6H8N1JNXrcjt7VMQ7gT7jL2rK and 7UvLGo8g2uf4evjwydePaaGnuXQ2
Neon projects: fragrant-hall-08272854 and quiet-mountain-99364667

Capacity is 7/10 in both Neon projects. The Preview branches are created and activated on Neon, but the Vercel action times out before the build starts. Full diagnostics and deployment links are in the post above. Thank you.

Correction: Neon’s official Discord invite itself is currently valid. The official short link and Discord invite API both resolve to the Neon server with no expiration, and the official Server Discovery page is live. Our local Discord UI showed “Invite Invalid,” so this was a client/session loading issue rather than an expired Neon invite. We are using the official Server Discovery and support email as parallel escalation paths.