Power Automate Limits and Config

%3CLINGO-SUB%20id%3D%22lingo-sub-1765993%22%20slang%3D%22en-US%22%3EPower%20Automate%20Limits%20and%20Config%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1765993%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20this%20document%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-automate%2Flimits-and-config%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-automate%2Flimits-and-config%3C%2FA%3E%2C%20can%20someone%20explain%20what%20run%20duration%20and%20retention%20mean%20on%20this%20chart%3F%20How%20would%20we%20configure%20our%20flows%20so%20they%20run%20automatically%20indefinitely%20based%20on%20our%20triggers%3F%20Some%20of%20our%20flows%20probably%20wouldn%E2%80%99t%20kick%20off%20every%2030%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1765993%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1768860%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20Automate%20Limits%20and%20Config%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1768860%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F396847%22%20target%3D%22_blank%22%3E%40ascquestions%3C%2FA%3E%26nbsp%3Bwhat%20they%20mean%20is%20that%20you%20can't%20have%20a%20flow%20that%20takes%20more%20than%2030%20days%20to%20complete.%20For%20example%20if%20you%20have%20an%20approval%20in%20the%20flow%2C%20if%20the%20approver%20doesn't%20approve%20or%20reject%20it%20in%20the%2030%20days%20then%20the%20flow%20will%20time%20out%20and%20won't%20complete.%20Any%20data%20in%20that%20flow%20that%20has%20been%20stored%20in%20a%20variable%20for%20example%20will%20also%20be%20lost%20after%2030%20days.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob%3CBR%20%2F%3ELos%20Gallardos%3CBR%20%2F%3E%3CFONT%20size%3D%222%22%20color%3D%22%23006400%22%3EMicrosoft%20Power%20Automate%20Community%20Super%20User.%3CBR%20%2F%3EIf%20I've%20answered%20your%20question%20or%20solved%20your%20problem%2C%20please%20mark%20this%20question%20as%20answered.%20This%20helps%20others%20who%20have%20the%20same%20question%20find%20a%20solution%20quickly%20via%20the%20forum%20search.%20If%20you%20liked%20my%20response%2C%20please%20consider%20giving%20it%20a%20thumbs%20up.%20Thanks.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

On this document: https://docs.microsoft.com/en-us/power-automate/limits-and-config, can someone explain what run duration and retention mean on this chart? How would we configure our flows so they run automatically indefinitely based on our triggers? Some of our flows probably wouldn’t kick off every 30 days.

5 Replies

@ascquestions what they mean is that you can't have a flow that takes more than 30 days to complete. For example if you have an approval in the flow, if the approver doesn't approve or reject it in the 30 days then the flow will time out and won't complete. Any data in that flow that has been stored in a variable for example will also be lost after 30 days.

 

Rob
Los Gallardos
Microsoft Power Automate Community Super User.
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

 

 

Thank you for your response! Some of our projects have approval processes that may go beyond 30 days per approval. What would you suggest we do in these cases? For example, a facilities project that goes through an agency which takes up to a year up to process and that approval is our condition to continue our workflow?

@ascquestions there's no way round the 30 day limit to achieve your approval times of over a year. So you will need to consider whether multiple flows can be triggered at different points in the process to keep within this.

 

Rob
Los Gallardos
Microsoft Power Automate Community Super User

Thank you for the response! We'll see about injecting some type of trigger every 29 days to keep the flow going.
I would take a look at this video, which includes some tips and techniques for long-running approval flows: https://youtu.be/h6Eb-F0P6Hs