An organization has a data-processing pipeline that runs on a V4 Azure Function App using the Consumption hosting plan. A specific HTTP-triggered function in the app usually processes webhooks in under 2 minutes. However, during periodic bulk uploads, the execution time for some requests increases to approximately 8 minutes, causing the executions to time out and fail. You need to adjust the function app configuration to allow a maximum execution duration of 8 minutes for these long-running requests without migrating to a different hosting plan. How should you configure the function app?
- AMigrate the function app to an App Service (Dedicated) plan, as the Consumption plan has a non-customizable execution limit of 5 minutes.
- Modify the host.json configuration file at the root of the function app to include the functionTimeout property set to '00:08:00'.Answer
- CAdd an application setting named WEBSITE_RUN_TIMEOUT with a value of 480 using the Key Vault reference syntax @Microsoft.KeyVault(SecretUri=...).
- DConfigure an App Service autoscale rule using Azure Monitor metrics to scale out the instances, which automatically extends the maximum execution window per function.
Answer
Modify the host.json configuration file at the root of the function app to include the functionTimeout property set to '00:08:00'.
The correct action is to modify the host.json configuration file at the root of the function app by setting the 'functionTimeout' property to '00:08:00'. In Azure Functions V4, the Consumption plan has a default timeout of 5 minutes, but it can be configured up to a maximum of 10 minutes. Because 8 minutes is within the maximum limit, migrating to another hosting plan is not required.
Step-by-Step Solution
Key Concept
Configuring execution timeout in host.json for Azure Functions V4
Estimated Time:1m 30s