web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Extend approval flow a...
Power Automate
Unanswered

Extend approval flow after 30 days

(0) ShareShare
ReportReport
Posted on by 1,599 Super User 2024 Season 1

Hello, 

 

I am looking for a way to extend and re-send approvals when the workflow has passed 30 days to ensure the workflow keeps running and the approvers keep having a chance to approval items (if not done within the first 30 days).

 

Essentially for Approvals going to Managers, we want them to be reminded every 7 days and once 30 days has lapsed, a new Approval flow should be generated and sent back to the manager again.

Equally for the Approvals going to Exec Directors, we want a new Approval flow to be generated after 30 days has lapsed.

 

Hope this makes sense to someone!!

 

Appologies for the exessively complicated workflow!

 

sudosaurus_0-1666875927179.png

sudosaurus_1-1666876037027.png

sudosaurus_2-1666876065704.png

sudosaurus_8-1666876391996.png

sudosaurus_4-1666876141462.png

sudosaurus_5-1666876212639.png

sudosaurus_7-1666876352848.png

sudosaurus_9-1666876453670.png

sudosaurus_10-1666876521778.png

sudosaurus_11-1666876553104.png

sudosaurus_12-1666876602292.png

sudosaurus_13-1666876643182.png

sudosaurus_14-1666876673063.png

<< START OF CONDITION "IF YES" BRANCH >>

sudosaurus_15-1666876772952.png

sudosaurus_16-1666876832749.png

ESSENTIALLY AFTER THIS STEP, WE WANT TO BE ABLE TO RESTART THE APPROVAL PROCESS FOR EXEC DIRECTORS AFTER 30 DAYS IF THE PREVIOUS APPROVAL TIMED OUT.

 

sudosaurus_17-1666876854796.png

sudosaurus_18-1666876892504.png

sudosaurus_19-1666876927232.png

sudosaurus_21-1666877026129.png

sudosaurus_22-1666877085751.png

sudosaurus_23-1666877110598.png

<< END OF CONDITION "IF YES" BRANCH >>

 

<< START OF CONDITION "IF NO" BRANCH >>

sudosaurus_24-1666877345927.png

sudosaurus_25-1666877389577.png

<< START OF CONDITION 3 "IF YES" BRANCH >>

sudosaurus_26-1666877427107.png

sudosaurus_27-1666877451637.png

sudosaurus_28-1666877478849.png

ESSENTIALLY AFTER THIS STEP WE WANT MANAGERS TO RECEIVE REMINDERS FOR THESE APPROVALS EVERY 7 DAYS UNTIL ACTION HAS BEEN TAKEN AND OBVIOUSLY NEW APPROVALS RE-GENERATED AFTER 30 DAYS HAS LAPSED.

sudosaurus_29-1666877500669.png

sudosaurus_30-1666877521940.png

sudosaurus_31-1666877571262.png

sudosaurus_32-1666877610218.png

sudosaurus_33-1666877640731.png

sudosaurus_34-1666877688772.png

sudosaurus_35-1666877717891.png

sudosaurus_36-1666877733824.png

ESSENTIALLY AFTER THIS STEP, WE WANT TO BE ABLE TO RESTART THE APPROVAL PROCESS FOR EXEC DIRECTORS AFTER 30 DAYS IF THE PREVIOUS APPROVAL TIMED OUT.

sudosaurus_37-1666877747455.png

sudosaurus_38-1666877767620.png

sudosaurus_39-1666877785288.png

sudosaurus_40-1666877834265.png

sudosaurus_41-1666877853673.png

<< END OF CONDITION "IF NO" BRANCH >> & << END OF CONDITION 3 "IF YES" BRANCH >>

 

<< START OF CONDITION 3 "IF NO" BRANCH >>

sudosaurus_0-1666893072731.png

 

Any help with this would be awesome!

 

Thanks

Chris 😀

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Categories:
I have the same question (0)
  • Pstork1 Profile Picture
    69,024 Most Valuable Professional on at

    There is no way to extend an approval flow instance past 30 days.  There are a couple workarounds that you might try.  the one that fits your scenario the best does require a Premium license, but it will work. Build two workflows.  One that uses the trigger you want to trigger the approval.  Have that flow call a second flow using an HTTP trigger. In the second flow do all the things you want the approval to do. Then either set a timeout on the Approval or build something into the Reminder loop so the flow deletes the approval after 28-29 days and then calls the HTTP trigger again to start another round of up to 30 days.  No individual flow will run for more than 30 days, but the process will repeat until the item is approved.

  • sudosaurus Profile Picture
    1,599 Super User 2024 Season 1 on at

    @Pstork1 

     

    Are there any examples for reference?

  • Pstork1 Profile Picture
    69,024 Most Valuable Professional on at

    This probably comes closest.  Calling a Child Flow is basically the same as invoking an HTTP trigger.

    Power Automate: Long-running Flows - Manuel T. Gomes (manueltgomes.com)

  • sudosaurus Profile Picture
    1,599 Super User 2024 Season 1 on at

    @Pstork1 

     

    This looks like it could make some sense to me! 🙂

     

    I've just mapped my workflow into 5 separate workflows in the attached document - I think this will make it much less complicated and as I can call other flows in the steps I'm hoping that will make this work I want it to.

     

    Thanks. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 250 Super User 2026 Season 1

#2
Expiscornovus Profile Picture

Expiscornovus 222 Most Valuable Professional

#3
Haque Profile Picture

Haque 174

Last 30 days Overall leaderboard