Power Automate long running Approval flows (beyond 30 days)

In this video on Power Automate long running Approval flows, we will explore building approval flows than span beyond the 30 day flow run duration limit.

Building long running approval flows in Power Automate ensures your approvers can have their approval action span beyond the 30 day flow limit.

Scenario is a Contracts Management approval workflow wherein the approval flow begins from Department review and then moves to Legal review for final approval.

We will create both a multi-step and a state machine approval workflow that can run beyond 30 days.

Topics covered:
✔️ Long running approval flows pattern
✔️ Multi-step approval workflow pattern
✔️ State Machine workflow pattern

#StateMachineApprovals #ApprovalsCookbook #Flow #PowerAutomate #Approvals #flowapprovals #PowerPlatform

[vpavan]

Brilliant Reza I am not sure how long you spent to get this breakthrough but I respect all your time and thank you a ton for sharing this super-advanced topic!

[JesterHammer]

One of the most valuable tutorials i’ve watched on Power Automate. Must watch for everyone. Reza is so far, my top online instructor on Power Automate. Will add his videos as part of our internal Power Platform practice training. Very valuable, thanks again.

[fleurwilliamson]

I’m watching this on Christmas Day 2020 and I feel like I just received the best Christmas present. Thank you Reza! So much better than the way I have been handling this. 💛

[breadandcheese]

@Reza - Hands down you are enabling others to learn and bring change in their companies. I very much enjoy your videos! Thank you!

[jherschel]

Awesome Video. And thanks for posting the workflow. just assigning all the approvals to myself and seeing it live in action saved me a lot of time and headaches. Thank you for being a great contributor to Power Automate!

[robofski]

What a creative way to use the Timed Out status of an approval action. I use it today to just send an email telling the requestor to resubmit but this is so much better! More rework for me :-) Another excellent video, thanks Reza.

[roylorenzo-ch]

You are the GOAT of Power platform. Thanks again.

[PValili]

This is a brilliant way of handling multi approval and timeouts in one flow structure

[radhikaM]

Brilliant video Reza. Now I can recreate my complex workflows without breaking my head. I might be little late for comments here, none the less, "#1 Power Teacher!! "

[rembautimes]

Its time to go thru all these cookbooks. Great resource Reza.

[patelbhargav]

I follow your instructions to impress people at work :D. Thank you Reza for making me look genius.

[premsai]

As always,

Quality Content Delivered (Period) . thanks a ton for your efforts for saving us a weeks of time in scratching our brains. 👏👏👏👏🙂🙂🙂.

[edwarddejesus]

Thank you so much Reza, it really helps me with my issue regarding the 30days limitation of Power Automate.

[johnsonjohn]

This is amazing, you have explained it with great clarity, Hats off!

[thanhthule]

Such a great, simple in an advanced way - video!!! I love this and all of your videos :)

[benoitappolonus]

Wonderful, Reza, you're amazing !

[karukarthi]

Very nice and much needed. Thanks a lot man for the superb video and in detailed..

[brettgovernanti]

Reza, this is an ingenious method for retriggering a step that has timed out and for logging histories on a multi-step Flow approval. These are important to my business process, kudos to you. I do have two issues, however. #1 Everything works as expected, except for when the timeout is reached; the Flow simply updates StartWF in SharePoint to 'Yes', then stops everything on the Terminate step. The run history reports that the flow has run successfully, however no new email notification appears to indicate that the Flow run on that step has, in fact, retriggered. The Flow run is simply done, full stop. I wonder if the condition on the trigger is actually getting touched?

[kylelane]

Still very relevant love the content and great tutorial!!

[kevinpham]

Hi Rezza, love the video. However, when i tried to implement this flow I noticed this scenario could happen. You stop the flow from retriggering with the field "StartWF" by setting it to "No" in the flow when you updated the item. But what happen while you are running the flow and you haven't hit the part where you update the flag to 'No' and the user in sharepoint updates the item. That would trigger another flow run and weird stuff can happen when the same flow is running multiple times. I also notice that flow doesn't run instantly the moment you create the item. It takes sometimes for flow to kick in and in that time the user can revise the item which can cause multiple flow runs as long as flag has not been set to 'No'.