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(252.8, 18%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
Following the instructions here: https://learn.microsoft.com/en-us/azure/logic-apps/edit-app-settings-host-settings?tabs=visual-studio-code#run-duration-and-history
I have set the 'Runtime.Backend.FlowRunTimeout' and 'Runtime.FlowRetentionThreshold' to 2 minutes (00.00:02:00) in host.json, but when running locally in vs code and when deployed to Azure the workflows are not expiring after two minutes.
Is there a maximum to these settings? I understand that the default is 90 days and it can be increased on single tenant APIs, but interested in what the maximum timeout is
@Robert Lawrie Thanks for reaching out. I do observe the same behavior at my end. Let me check with my team on what is the minimum/maximum value that can be set for Runtime.Backend.FlowRunTimeout
@Robert Lawrie Apology for the delay. I have got confirmation from my team that there is no maximum value that can be set for Runtime.Backend.FlowRunTimeout. You can set this value as per your requirement. In case, if you are facing any issue with any of the values then please share the repro so I can reach out to my team.
Thanks very much @MayankBargali-MSFT , I still am seeing the issue where the 'Runtime.Backend.FlowRunTimeout' setting doesn't have any affect - did you reproduce this at your end?
@Robert Lawrie Can you share the action that you are using and what value you are setting up. It could be that changing this setting is not what you actually want to be doing in case of some of the actions such as delay. If you can confirm what action/workflow you are using and I can repro the same and reach out to my team.
Thanks @MayankBargali-MSFT
For some background, we want to increase the workflow timeout as in our production logic app instance we make use of web hooks, which can remain in 'waiting' state for more than 90 days (the default workflow timeout) and so we end up with broken workflows as the workflow times out before the webhook is triggered.
So I wanted to test the workflow timeout setting and to use a very short timeout to aid with testing. I set the timeout to two minutes, then used a webhook action which, at runtime, enters 'waiting' state for more than 2 minutes without causing the workflow to expire.
My host.json file is as below:
{
"version": "2.0",
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
"version": "[1.*, 2.0.0)"
},
"extensions": {
"workflow": {
"settings": {
"Runtime.FlowRetentionThreshold": "00.00:02:00",
"Runtime.Backend.FlowRunTimeout": "00.00:02:00"
}
}
}
}
@Robert Lawrie Thanks for sharing the details. I will check with my team and will keep you posted.
![](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(140.8, 79%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVK%3C/text%3E%3C/svg%3E)
@MayankBargali-MSFT @Robert Lawrie , Were you guys solved this issue? I need to setup workflow timeout but not getting any relevant documentation.
We haven't looked again at this issue, but it strikes me that with my testing I was expecting the workflows to timeout based on Runtime.Backend.FlowRunTimeout, whereas there is another setting documented here https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-limits-and-config?tabs=standard%2Cazure-portal#tabpanel_1_standard 'Runtime.FlowMaintenanceJob.RetentionCooldownInterval' which defaults to 7 days and controls how often the timeout is checked and acted upon. So it might be that if this is reduced the FlowRunTimeout would be easier to test
@Robert Lawrie Thanks for the response. I have gone through the link but that settings is to check for the run history and remove all old runs from history. In the link they talk about Run duration but no where mentioned how to configure this value.