How can I split the main flow (Flow A) into two or three flows (Flow B, Flow C) for execution?

(0) Share

Report

Posted on by PC-13100726-0

Hello All,

This workflow requires multiple departments to complete approvals before an employee’s last working day after the employee submits a request via Power Apps. If a request is submitted more than 60 days in advance, we run into 30-day timeout issues. How should I break up the flows so that:

Flow A: Create an approval → update items in SharePoint (store the Approval ID) → then complete.
Flow B: Run daily to check whether Flow A already has an approval record; if yes, update the SharePoint items (Approver Name, Approval Time, Approval Outcome). (Maybe use "Do Until" action to let the process could last more than 30 days)
Flow C: Run daily to check whether all approvers covered in Flow B have approved; if so, send the final Create an approval to the last department.

Here is part of the Flow A, is there any ideas to split the main flow into 2 or 3 flows?

I met an issue that "wait for an approval" has timed out... and be completed automatically.

Any input would be appreciated. Thank you all!

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

developerAJ 4,763 on at

Like (1)

Report
Copy link

Link copied!

I personally prefer Outlook Actionable Messages. You can find YouTube videos about it. Using Actionable Messages can help you achieve your end goal in an even better way

Was this reply helpful? Yes No
PC-13100726-0 4 on at

Like (0)

Report
Copy link

Link copied!

@developAJ

Appreciate your input! 😊

I tried Outlook Actionable Messages, and it seemed that this step also needs to wait for approver's action.

I’m concerned that if it exceeds 30 days, the process will still be automatically terminated. 😥

Thanks for let me know a new action that I've never thought!

Was this reply helpful? Yes No
Suggested answer

MS.Ragavendar 7,160 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
@PC-13100726-0,

While seeing the visual of the flow, it showing the approvals are parallel if they approval are sequential based , We can create a status column in the backend based on the Outcome of the approval the status column needs to be updated once its update we have start the appropriate workflow in this way you can segregate the flows.

For e.g

Initial Approval - 1st Flow (Manager)

Once the flow is approved the status column in the backend set as IT

Using SharePoint modified trigger watch out for that column value (Condition based trigger) If its IT you can start the (IT) and based on the outcome start the other flow

With respect to the Timeout, we don't have an control but there is alternate way to extend the timeout as well.

https://www.matthewdevaney.com/extend-a-power-automate-approval-over-the-30-day-limit/.

Another approach, Instead of moving with the approvals create a respective form in the power apps itself and using deeplink sent the item to the user act them to take an action on that based on the user action you can create respective forms and update the backend status accordingly.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.

❤️ Please consider giving it a Like, If the approach was useful in other ways.

🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.

Was this reply helpful? Yes No