Quick answer
Render documents pre-deploy duration as 30 minutes. Pre-deploy runs after build and before the new service version starts.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| pre-deploy durationPre-deploy runs after build and before the new service version starts. | 30 minutes | Eligible services | RenderAug 22, 2026 |
Why does this limit matter?
A database migration can succeed in build but still block the deploy at the shorter pre-deploy ceiling.
This value is scoped to Eligible services; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Time migrations independently and inspect pre-deploy rather than build logs.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- The command should be safe to retry and should not hold unbounded database locks.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related