| title | description | services | author | ms.service | ms.topic | ms.date | ms.author | ms.custom |
|---|---|---|---|---|---|---|---|---|
include file |
include file |
functions |
nzthiago |
azure-functions |
include |
02/21/2018 |
nzthiago |
include file |
The timeout duration of a function app is defined by the functionTimeout property in the host.json project file. The following table shows the default and maximum values in minutes for both plans and the different runtime versions:
| Plan | Runtime Version | Default | Maximum |
|---|---|---|---|
| Consumption | 1.x | 5 | 10 |
| Consumption | 2.x | 5 | 10 |
| Consumption | 3.x | 5 | 10 |
| Premium | 1.x | Unlimited | Unlimited |
| Premium | 2.x | 30 | Unlimited |
| Premium | 3.x | 30 | Unlimited |
| App Service | 1.x | Unlimited | Unlimited |
| App Service | 2.x | 30 | Unlimited |
| App Service | 3.x | 30 | Unlimited |
Note
Regardless of the function app timeout setting, 230 seconds is the maximum amount of time that an HTTP triggered function can take to respond to a request. This is because of the default idle timeout of Azure Load Balancer. For longer processing times, consider using the Durable Functions async pattern or defer the actual work and return an immediate response.