Why is Logic App creating another run when the http action is taking more than 1 min to complete?

Question

Why is Logic App creating another run when the http action is taking more than 1 min to complete?

Vivek Komarla Bhaskar 956

Hi,

In my logic app, when my HTTP action takes more than 1 minute to complete, it creates a new run, while the existing run is also running in parallel.

Is there a way to ensure the logic app doesn't create a new run in this case? In addition, what is the option to increase the retry time?

Could you please help me with both options to disable retry and increase retry time?

1 answer

Your answer

Answer 1

MayankBargali-MSFT 70,936 Moderator

@Vivek Komarla Bhaskar Thanks for reaching out. Are you using a Timmer trigger that triggers your logic app every one minute? Inside your workflow you have HTTP action that calls your HTTP endpoint. Another run should not be created until and unless some event is triggering your logic app. The HTTP limit is documented here for different environments and yes you can disable the retry by navigating to the setting of your HTTP action and select None on the retry policy.

You cannot increase the timeout duration for the consumption logic app. In case if you are using standard logic app then you can update this configuration (Runtime.Backend.HttpOperation.RequestTimeout).

User's image

Feel free to get back to me if you have any queries or concerns.

Please accept as "Yes" if the answer is helpful so that it can help others in the community. If you need any help/clarification/concerns/follow up questions, then please click on "Add Comment" on my answer and provide more details.

Vivek Komarla Bhaskar 956 Reputation points

2023-03-14T11:41:31.6966667+00:00

Hi @MayankBargali-MSFT

I already tried to set the Retry Policy to None but still, I see a run being initiated. Maybe because I have a recurrence step which runs the logic app every 5 mins. Is there a way to not allow the logic app to run again when its already running?
MayankBargali-MSFT 70,936 Reputation points Moderator

2023-03-14T11:53:33.42+00:00

@Vivek Komarla Bhaskar The configuration that you are setting is on the action, so it is applicable on at the action level. So, if you want to execute only one run at the time so you need to change the setting at the recurrence level (i.e. trigger) and enable the limit and set the Degree of Parallelism to 1.

Once you set this to 1 so there will be only one run executing at a time but in case if there are any other occurrence that triggers that all the other runs would be in the waiting state. Only one run will be executed at a time. You may see multiple run's status as Waiting in this case. Unfortunately, there is no out of box feature to skip these waiting run's.
Vivek Komarla Bhaskar 956 Reputation points

2023-03-14T13:27:56.89+00:00

After making these changes, the HTTP action fails once the time exceeds 1 minute. Despite setting Timeout and choosing asynchronous, it still fails. What is the process for increasing the timeout?
MayankBargali-MSFT 70,936 Reputation points Moderator

2023-03-15T04:44:48.9933333+00:00

@Vivek Komarla Bhaskar You cannot change the request timeout duration for standard logic app. If you see in the screenshot that you have shared the action timeout is set to 5 minutes but in note it clearly states this does not alter the request timeout in single request.

For consumption output request is 2 min but looks like your service is timing out. Are you passing any timeout parameter in the query parameter/body. Have you tested your API outside logic app and what was the outcome? The request should not be timed out up to 2 minutes from logic app end until the server is closing it.

In case if it is above the limit as documented here then please refer to the tip below.

For longer running operations, use an asynchronous polling pattern or an "Until" loop. To work around timeout limits when you call another workflow that has a callable endpoint, you can use the built-in Azure Logic Apps action instead, which you can find in the designer's operation picker under Built-in.

Share via

Why is Logic App creating another run when the http action is taking more than 1 min to complete?

1 answer

Your answer