multi members approval processes in Flow Designer

[SYCTC001]

I am seeking advice on designing multi-stage approval workflows within Flow Designer.

In Japan, sequential approval processes (e.g., Manager → Department Head → Division Director) are standard business practice.

However, the default "Ask for Approval" action appears primarily designed for concurrent approvals—either in parallel or with conditional logic like "first-to-approve" or "all-must-approve."

I would appreciate your insights on the following:

Sequential "Ask for Approval" actions:

Is it considered best practice to chain multiple "Ask for Approval" actions sequentially in a single flow?

If so, what are the potential risks or performance implications I should be aware of?

[yashkamde]

Hello @SYCTC001 ,

Yes ! The Ask for Approval action is asynchronous, when it fires, the flow moves into a waiting state and the execution context is released and it resumes only when the sysapproval_approver record is updated (approved/rejected) and an event fires.

But you can't just use one "Ask for Approval" with a multi-approver list set to sequential order that works when the approver pool is fixed and known up front, but not when Stage 2 approver depends on who Stage 1 approver was (e.g., "the manager's manager," looked up via chain, or a department-to-director mapping table).

For that you can use it with a Decision Table OR subflow + loop, and you'll have something that scales across departments without becoming an sequential actions.

If my response helped mark as helpful and accept the solution.