Allow running for greater than 10 minutes on a Consumption plan
The current limit of 10 minutes is not viable for some processing scenarios we have. We cannot use Durable Functions to solve our processing needs either. We simply need more time. Let us configure a longer timeout than 10 minutes and pay you for the run time. :)
Thank you for the feedback! Currently, the Premium Plan supports this use scenario with Durable Functions. However, it is not planned currently to support this in a Consumption Plan.
Looks like the Premium Plan times out at 60 minutes? Any plans to make it unlimited?
Alan M commented
Please ensure this allows for the execution of functions with an infinite timeout. Using durable functions is an undesirable workaround solution because the programming model does not work well with code bases that internally perform very long running operations, and too much business logic ends up being intertwined in the functions for orchestration contexts and activity functions that results in hard to maintain code. Ideally one should not have to change the programming model used to execute long running operations in a serverless deployment.
Any kind of limit that is meant to "prevent runaway executions" is not wanted. If someone writes flawed code that results in a runaway execution, that is a risk they should be allowed to take and accept the financial implications of that occurring.