Azure Standard Tier Logic App - Timing Out After 3.75 Minutes

Question

Azure Standard Tier Logic App - Timing Out After 3.75 Minutes

Anonymous

Hello

We are currently working on an Azure Logic App implementation that conducts file format scans on large external client data files within Blob Storage. The files we are handling can reach sizes up to 25GB+ for a single zip file.

For a 20gb file for example, the function app took 6 minutes to complete and we have a Logic App that is checking for completion of the function app which then performs a notification actions.

Our challenge lies in the default timeout limit for single tenant apps, where the Logic App times out after 3.75 minutes. Despite our efforts to extend the timeout limit, we are still encountering issues.

Here are the configurations we've attempted:

Logic App standard + stateful + high-end configuration available for the app service plan.
Updated timeout limits using the documented approach (https://learn.microsoft.com/en-us/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal):

Workflows.RuntimeConfiguration.RetentionInDays=90.00:00:00
Runtime.Backend.FlowRunTimeout=90.00:00:00
Runtime.FlowRunRetryableActionJobCallback.ActionJobExecutionTimeout=00:10:00

Despite these adjustments, the Logic App still fails at the default interval.

We would appreciate your guidance on how we can effectively increase the timeout limit or find a workaround to overcome this limitation.

Thank you for your assistance.

Kind regards,

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Azar 31,630 MVP Volunteer Moderator

Hi Marc Hedgley

Dealing with large file processing really is a frustrating job sometimes and i guess you've taken the right steps already by adjusting the settings, there are a few additional considerations I can recommend.

Instead of processing the entire 25GB file in a single run, consider breaking it down into smaller chunks and processing them in parallel. This way, each smaller chunk has a better chance of completing within the timeout limits.

Rather than processing the entire file synchronously within a single function call, you can design your Azure Function to handle chunks of the file asynchronously. Use Azure Queues, and Azure Service Bus to trigger subsequent processing for each chunk.

and finally, Azure Durable Functions allows you to write stateful functions in a serverless environment. It's designed to handle long-running operations and can be used to implement workflows that span multiple functions.

Hopefully, this helps, kindly accept the answer if you find it useful thanks much.

Anonymous

2023-12-20T14:08:16.3933333+00:00

Thanks Azar, this is useful. We are looking at the Azure Durable functions as part of a long-term strategic solution to resolve the issue as we expect file sizes to increase overtime. Are you aware of any configuration changes we can make to increase the timeout limit of Logic Apps?

Kind regards

Marc
Azar 31,630 Reputation points MVP Volunteer Moderator

2023-12-20T15:51:29.6866667+00:00

Hi again

The timeout limits are managed separately for each service you have. For Azure Logic Apps, you can configure the timeout at the Logic App level, while for Azure Durable Functions, you have more granular control at the task level.

Let me help you with Configuration:

Per Logic App Run

In the Azure Portal, navigate to your Logic App.

Go to the Logic App designer.

Select the "Settings" menu.

Adjust the "Timeout" setting as needed.

It is imp to note the maximum timeout for a Logic App run is 120 days

for more details its good idea to follow documentations.

https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-limits-and-config?tabs=consumption%2Cazure-portal

and also regardless of the configuration, long-running operations may still need to be broken down into smaller as told before.

Kindly accept if this helps thanks.
Azar 31,630 Reputation points MVP Volunteer Moderator

2023-12-22T06:21:35.99+00:00

Hi Marc Hedgley

Checking if the answer provided above was useful, if it did, kindly accept and upvote thanks much.
Anonymous

2023-12-22T15:28:05.73+00:00

Hello Azar, thank-you yes that answer was really useful. We have made the suggested optimisations as well as implementing an Until Loop which has increased performance somewhat however we are still seeing the timeout error. Strategically, we are looking at change to an Azure Durable function to see if we can extend the operation run time.

Thanks

Marc

Share via

Azure Standard Tier Logic App - Timing Out After 3.75 Minutes

0 additional answers

Your answer