Quick answer
Azure Functions documents hosting-plan execution timeout as Consumption: 5m default, 10m max; other plans: 30m default, unbounded max with caveats. The functionTimeout host.json setting controls the app within the plan ceiling.
Verified Sep 17, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| hosting-plan execution timeoutThe functionTimeout host.json setting controls the app within the plan ceiling. | Consumption: 5m default, 10m max; other plans: 30m default, unbounded max with caveats | Hosting-plan specific | MicrosoftSep 17, 2026 |
Why does this limit matter?
Changing hosting plans can alter the allowed function duration without changing the application's HTTP path.
This value is scoped to Hosting-plan specific; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm hosting plan and inspect functionTimeout in the deployed host.json.
- 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
- Microsoft now labels the Consumption plan legacy (Linux Consumption retires 30 September 2028); Flex Consumption, Premium, Dedicated and Container Apps default to 30 minutes with an unbounded maximum.
- 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