How can I increase the timeout for Azure Consumption plan for more than 10 mins

Dinesh Prajapati 126 Reputation points
2023-02-06T12:22:56.4+00:00

How can I increase the timeout for Azure Consumption plan for more than 10 mins.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,257 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Khurram Rahim 1,841 Reputation points
    2023-02-06T19:57:04.28+00:00

    Azure Functions in the Consumption plan have a default timeout of 5 minutes and an upper limit of 10 minutes. If you need a longer timeout, you need to switch to a different plan, such as the Premium plan, which provides longer timeouts and dedicated resources.

    Here's how you can change the plan:

    1. Go to the Azure portal and navigate to your function app.
    2. Click on the "Function app settings" link.
    3. Under the "Configuration" section, click on the "General settings" link.
    4. Change the "App Service Plan" to the desired plan (e.g., Premium).
    5. Save the changes.

    Note that switching plans can impact your costs, so make sure to review the pricing information for the new plan before making the change.


  2. MughundhanRaveendran-MSFT 12,421 Reputation points
    2023-02-09T08:44:34.8366667+00:00

    @Dinesh Prajapati ,

    The max timeout limit for a Function app running on Consumption plan is 10 minutes. As mentioned by others, you will have to change your plan to Dedicated App service plan or Premium plan. These plans do not have a timeout limit. Timeout limit is specific to Plan/SKU and not related to Windows/Linux. So for a Linux consumption plan, the timeout limit is 10 minutes. You will have to optimize the code to complete the execution within 10 minutes or upgrade to a higher SKU ( Premium/Dedicated ASP).

    https://learn.microsoft.com/en-us/azure/azure-functions/functions-scale#timeout

    Please note that, for HTTP trigger function running on any plan/SKU, the time out limit is 230 seconds. This is the internal load balancer timeout that is specific to http trigger. To overcome this, you can leverage durable functions.

    https://learn.microsoft.com/en-us/answers/questions/758823/httptrigger-response-timeout

    https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/web-apps-performance-faqs#why-does-my-request-time-out-after-230-seconds