Handle optional Power Automate approvals in one cloud flow
Diesen Beitrag auf Deutsch lesen
Use conditions, explicit outcomes and separate rules to run only the Power Automate approvals a request needs, without duplicating shared process steps.
Original article from November 9, 2026: Power Automate: Handle Optional Approval Steps Without Creating Separate Flows, by Softchief Author, on Softchief Technologies. Read the original
This is our own summary, not a republication or full translation.
TL;DR
Power Automate can use Conditions or Switch actions to run optional manager and finance approvals in one cloud flow. Initialize outcomes such as Not required before each branch, update them when approvals run, then test approved, rejected, skipped and unanswered paths before using the flow.
Why it matters
- Makers: Define approval rules in plain language, use Conditions or Switch actions, and initialize skipped outcomes so downstream steps can distinguish Not required from Approved or Rejected.
- Makers: Keep shared updates and notifications after approval branches, then test every required, skipped, rejected and unanswered route in run history.
- Leadership/Business: Confirm thresholds, boundary values, currencies and rejection or timeout handling with process owners before the flow is built or changed.
Frequently asked questions
How can Power Automate skip an optional manager approval without creating another flow?
Place the approval inside a Condition branch and continue with shared actions after the branch. The skipped path should receive an explicit Not required outcome.
How should a Power Automate flow track an approval that did not run?
Initialize an outcome variable before the condition with Not required, then replace it with the approval result when the branch executes.
How should optional Power Automate approvals handle rejection and no response?
Check approval outcomes after each approval and define separate handling for rejection, timeout or failed actions. Test each case and review the run history.