Do Until doesn't cancel when it times out after 30 days

[jrivera]

I'm noticing an odd behavior with expired flows that have a do until.  I have a do until with a timeout of 30 days and a limit of 60.  Inside is a switch.  In the default branch, I update a SharePoint list item, send an email with options, then if a condition is met, the status is updated to a status that will allow the switch to move to the next branch.  If a user doesn't click the button in the email to allow the status to be set and 30 days go by, instead of timing out, the loop continues and tries the remaining number of times (60).  The screenshot shows the email action timed out but what happens is that email is sent each time the loop happens so the users are getting 50+ emails when it should've expired.  

Thanks,

Jason

[Mike_Guzowski]

Hm, I think it is connected to flow limitations that is:

1. max 30 days for flow duration

2. max 30 days for approval duration 

From documentation: "Includes workflows with pending steps like approvals. After 30 days, any pending steps time-out. Timed-out approvals are removed from the approvals center. If someone attemps to approve a timed-out request, they’ll receive an error message."

So you don't really want someone to make your flow wait for more than 30 days. However if you know that such case have to be covered you can build special architecture of your flow as Serge Luca described in his blog

[Inpriya01]

Hello Jason

we Are facing similar issue, did you find any way to fix this issue. If the flow is expired we don’t want to send 50+ Emails. 

Seems it runs remaining count of iterations which is meaningless when flow is expired.