Quick answer
Render documents maximum build duration as 120 minutes. Only one build is active for a service at a time.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum build durationOnly one build is active for a service at a time. | 120 minutes | Build pipeline | RenderAug 22, 2026 |
Why does this limit matter?
Slow dependency installation can block later deploys as well as fail the current build.
This value is scoped to Build pipeline; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Break CI logs into dependency, compile, upload, and deploy phases before optimizing.
- 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
- Pre-deploy and service-start phases have separate clocks.
- 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