[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Build fails before start: Resource provisioning failed (Neon)

98 views · 0 likes · 2 posts


Pkoson (@pkoson) · 2025-12-21

### **Post content**

Hi,

I’m hitting a blocking issue with **Resource Provisioning** that makes the project completely undeployable.

The deployment fails **before the build starts**, logs never load, and the process always stops at:
```
Provisioning Integrations
Neon: Create database branch for deployment

```

This is **the exact same issue** described here:
[https://community.vercel.com/t/build-failed-resource-provisioning-failed-build-logs-not-loading/21495](https://community.vercel.com/t/build-failed-resource-provisioning-failed-build-logs-not-loading/21495?utm_source=chatgpt.com)

### **Timeline / what happened before it broke**

Initially, deployments were working **almost fine**:

1. The build actually started and progressed normally.
2. It then failed **during the build** due to:
  * an **outdated Next.js version**
  * reported vulnerabilities / security warnings.

At this stage:

* provisioning completed successfully,
* build logs were available,
* the failure was a standard build failure (not related to provisioning).

Next:

3. Vercel automatically created a **GitHub branch** suggesting an update to the Next.js version.
4. I merged that **GitHub branch** into my main branch after updating Next.js and fixing the reported issues.

After this merge:

5. Deployments stopped working entirely.
6. The build **never starts**.
7. Build logs are no longer available.
8. Every deployment now fails at **Resource Provisioning**, before the build phase.

At this point, the project appears to be stuck in a broken provisioning state.

The project is effectively **bricked** due to a stuck provisioning state.


system (@system) · 2026-01-20

Hi @pkoson!

I'm the Vercel Community Bot, and I'm here to help make sure your question gets answered quickly!

To help our community team assist you better, could you please provide:

• **Code snippets**
• **Error messages**
• **Config files**
• **Deployment/build logs**

Having this information will help us identify and solve your issue much faster. For more tips on getting great answers, check out [How to Get Good Answers](https://community.vercel.com/t/how-to-get-good-answers/158). Thanks!