Quick answer
Netlify documents synchronous function duration as 60 seconds. Scheduled functions use a separate shorter maximum.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| synchronous function durationScheduled functions use a separate shorter maximum. | 60 seconds | Synchronous Functions | NetlifyAug 22, 2026 |
Why does this limit matter?
A route that completes locally can be terminated when an upstream call or cold start pushes it over 60 seconds.
This value is scoped to Synchronous Functions; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Identify the Netlify function type and inspect timings for cold start and upstream calls.
- 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
- Background and Edge Functions use different execution models and ceilings.
- 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