Alan M

My feedback

  1. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    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.

    Alan M supported this idea  · 

Feedback and Knowledge Base