LogicApps Delay Billing

Question

LogicApps Delay Billing

Ben McGarry 26

When a logic app is currently on a delay is it billed?

For example if a logicapp had to pause for 1 hour due to API rate limits, would that 1 hour be billed or would it be as if the LogicApp wasn't running in the first place.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Mike Urnun 9,792 Moderator

Hi @Ben McGarry

Logic Apps doesn't know that its requests are being throttled from the destination service and stops automatically. Rather, Logic Apps makes it as easy as possible for you to orchestrate your workflow to account for such scenarios. The following is a good read on this matter: Destination service or system throttling

If requests fail (due to rate-limiting or any other reasons from the destination API), Logic Apps will keep trying as per your Retry policy (default is 4 attempts) and your workflow run should halt/fail or timeout per built-in limits as applicable - so the billable executions are original request+retries. But if your workflow is such that your Logic Apps keeps running and retrying the API during the entirety of 1 hour, billable executions will be more and you'll be charged accordingly.

Ben McGarry 26 Reputation points

2020-11-12T22:37:00.693+00:00

If I said had it loop through 100 requests (by counting up to 100), then pause for 2 minutes, then loop through another 100 until complete. Would i be billed for that 2 minute pause or just the requests?
Mike Urnun 9,792 Reputation points Moderator

2020-11-12T23:06:17.673+00:00

If you're using the Delay connector to achieve the 2min pause, which Logic Apps is still allocating compute resources under the covers to help you achieve that 2min pause, so you'll be charged accordingly for the price for Actions from the Delay connector:

Disclaimer: Pricing above is subject to change.

You'll want to fine-tune your workflow to the destination service as accurately as possible in order to arrive at an estimated cost per run. In your example, if you shoot off 100 requests from a loop and if some of those requests timeout or fail on the network, retry attempts (which are all billable executions) will be occurring behind the scenes, so what may seem like 100 successful requests at the end might have been made possible by more than 100 requests and corresponding executions under the covers.
Ben McGarry 26 Reputation points

2020-11-13T00:10:45.097+00:00

Based on the above would a 2 minute delay be classed as one execution and billed at solely the rate shown? Or is it that rate per execution time so if it lasts 120 seconds it’s that rate x 120.
Mike Urnun 9,792 Reputation points Moderator

2020-11-13T00:44:37.183+00:00

Pretty sure it's based on the number of executions rather than how-long it runs to delay a workflow so it would be one execution billed solely at the rate shown. I have just sent a note to the Logic Apps team to confirm, please stay tuned.
Mike Urnun 9,792 Reputation points Moderator

2020-11-13T02:13:21.11+00:00

I confirmed that the duration of the wait is not factoring in and you’re charged per execution per run instance basis. Hope this helps.

Share via

LogicApps Delay Billing

0 additional answers

Your answer