cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
eBentl
Advocate I
Advocate I

Flow timeout duration

I'm about to set up a multi-staged approval which could take a while to run and have come across the below pages discussing the timeout duration for automated Flow's being increased from 30 to 90 days.

https://docs.microsoft.com/en-us/business-applications-release-notes/April19/microsoft-flow/planned-...

https://docs.microsoft.com/en-us/business-applications-release-notes/April19/microsoft-flow/increase...

 

Article one suggests that this functionality became GA last month, while page two suggests it isn't released yet. Can anybody confirm if this change has been actioned yet?

1 ACCEPTED SOLUTION

Accepted Solutions
v-bacao-msft
Community Support
Community Support

 

Hi @eBentl ,

 

As mentioned in the link you provided, MS Flow is now extending the available lifetime of automated flows from 30 days to 90 days.

But it seems that this feature is not currently available from my quick test.

The current Flow run duration is still 30 days, please check online doc:

https://docs.microsoft.com/en-us/flow/limits-and-config#run-duration-and-retention

If there are any new updates, we will post it in time, and you could also follow the MS Flow blog for more information on product updates.

https://flow.microsoft.com/en-us/blog/

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

7 REPLIES 7
manuelstgomes
Super User II
Super User II

Hi @eBentl 

 

I think the official information from Microsoft is that it is 30 days.

https://docs.microsoft.com/en-us/flow/limits-and-config

 

I think they'll update the documentation once this limit changes.

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

v-bacao-msft
Community Support
Community Support

 

Hi @eBentl ,

 

As mentioned in the link you provided, MS Flow is now extending the available lifetime of automated flows from 30 days to 90 days.

But it seems that this feature is not currently available from my quick test.

The current Flow run duration is still 30 days, please check online doc:

https://docs.microsoft.com/en-us/flow/limits-and-config#run-duration-and-retention

If there are any new updates, we will post it in time, and you could also follow the MS Flow blog for more information on product updates.

https://flow.microsoft.com/en-us/blog/

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

The timeout duration has not yet changed.   Hope Microsoft makes this a priority, thirty days is NOT enough.  

Anonymous
Not applicable

An update from Microsoft on this would be good. If it's in backlog surely helping us understand when it will go into sprint. 

 

30 days is causing us lots of timeout issues. 

OlafStetzer
Advocate I
Advocate I

My understanding from reading the article behind the original link 

https://docs.microsoft.com/en-us/business-applications-release-notes/April19/microsoft-flow/increase...

is that the longer lifetime is only available within CDS managed flows (or by using the new versions of connectors).

Is it sufficient to add existing flows to a solution within CDS or does one need to do anything else?

I do not understand the implications of the last Paragraph:


In addition to the long-lived approval processes, flows built on Common Data Service that use the Common Data Service (current environment) connector can now last for up to one year - much longer than the current limit of 30 days. Like the solution flows that can be activated automatically on import, for a flow to have its runs last up to one year, it must only leverage the Common Data Service (current environment) connector and built-in actions.

 

krschutte
New Member

More than a year later and the 30 days flow timeout has still not changed?

30 days does not meet the needs for real world business processes.

 

Can this please somehow be prioritized?

 

OlafStetzer
Advocate I
Advocate I

My experience from the last months is that the timeout has not changed.

What is even more annoying: The history of flow executions is also only 30 days still.

Which means, when a flow has been cancelled due to timeout, the flow history
does not show this instance shortly after the timeout occured with no means to inspect
the flow details of the the failed flow.

Helpful resources

Announcements
MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MSFTBizAppsLaunchEvent

Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (44,206)