cancel
Showing results for 
Search instead for 
Did you mean: 

Flow run history

I understand this was recently changed to 30 days. With run limit and history both at 30 days this makes it impossible to trouble shoot some issues that may not be noticed until after the run timeout. For example I had an approval flow that timed out but right before it did it sent 60+ approval emails again before fully timing out. when going to figure out why it sent 60+ emails i couldn't due to the change in flow history retention. 

Status: New
Comments
dmarronj
Advocate I

Hello, I fully support this request.

It would be very useful to expand the run history to 60 days at least, so you have a 30-day time for running, and another 30-day time for troubleshooting in case an error occurred at the end of those first 30 days.

Right now if there's a problem in day 29 of execution and it was a weekend, I cannot troubleshoot what was wrong in the execution.
Thanks.

Lucian
Resolver I

Well, flow run history for 30 days were "better times"... now is just 28 days because of some GDPR rules.

And now will come the problems - because the default "time out" for a flow is 30 days when the run history is only 28 days.

Recently I had a problem with a flow that passed that 28 days and received an email telling me that I have one failed run... but with no option to see what really happened there. With the help of the MS Support I could only find out that was a "time out", but why/where or any other detail were impossible to get.

 

So, please - extend the run history at least couple of days beyond the "default time out".

Thanks