This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 42%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Hi
What is the max possible value for Delay-Until action in Logic App? Can it be 2 years in future?
How does the cost/pricing works in this regard. Do we get charged for the time while the action is being "delayed"?
Regards
A Logic app cannot run for more than 90 days in stateful workflows, 5 minutes for stateless and 366 days in a ISE environment logic-apps-limits-and-config. Therefore it would be safe to say the delay action cannot run for longer than the workflow run duration.
@Adnan Khan For your first query I have reached out to my team to confirm if there is any max value for the delay until as I don't see any limit documented here and will keep you posted.
For your second query for your run instance as there is no polling happening while the delay timer is running. You only pay for one (1) billable execution for the entire duration of the wait.
Update:
I have got the confirmation from the team that the max wait in the delay action is the same as the flow run duration value as documented here.
Thanks @MayankBargali-MSFT - looking forward for an update once you get an answer from the team.
Good to know about the billing details.
But in a state where it is "delayed-until" is it actually still running?
If so what other tools does Azure provide if we need to schedule task to be run in future (both near-time and far-away? As in could be minutes in future but also year.
@Adnan Khan In scenario if you are using the multiple tenant environment (i.e. consumption SKU) the max time duration is 90 minutes. So in case if your business logic runs for 5 minutes before the delay until action and you have specified delay until action with the value of 90 minutes then your workflow will timeout at the 85th minute on the wait until action. As the total duration can only be 90 mins (5 + 85 minutes).
Hope the above examples clear things up. If your requirement is to wait for 2 years then you need to use event driven architecture where your service (where you are waiting to be completed or any action that needs to be taken) will send the event to another logic app to notify if it has completed processing. In case if you are looking for approval base worflow then you can refer to this document.
@Adnan Khan I have updated my answer with the confirmation from my team. @Alistair Ross mentioned the same in his answer.
Thanks @MayankBargali-MSFT - yes @Alistair Ross explained this in detail below.
So what if our requirement is not to wait for 2 years but just that we need something to be triggered after a year or two? Is there really no tool on Azure for this type of work?
@Adnan Khan If you want to trigger something in the future then I suggest using a service bus. In your main workflow instead of using the wait until action, you will use the service bus send message action to send the message to the service bus with the property ScheduledEnqueueTimeUtc so the message is scheduled for the future time. Based on your business logic the message will only be visible to consumed on the future date and time and now you can consume that message. You can create another logic app that will get triggered once the message becomes active on a future date.
You can refer to different trigger available in the service bus connector to trigger your new logic app and continue your business workflow.
Hope the above helps. Let me know if you have any queries or concerns.