Reliable Power Automate approvals: substitution, reminders and escalation
The most expensive approval failure is often not technical: nobody makes the decision in time. If a workflow depends on one person's mailbox, it will eventually stop. Substitution and escalation should be part of the first production design.
1. Do not hard-code approvers in the flow
Resolve decision makers from organisational data, configuration or business roles so changes do not require editing every flow.
- Entra or organisation data
- configuration table
- business role
- fallback owner
2. Make substitution explicit
A substitute should not be an ad-hoc forwarded email. Store who substitutes for whom, the validity period and the scope of that delegation.
- substitute person
- start and end date
- scope
- audit
3. Reminder and escalation are different
A reminder asks the same decision maker again; escalation changes the decision path or involves another level. Give them separate timing and states.
- reminder cadence
- escalation threshold
- new decision maker
- overdue state
4. Make waiting visible
For long-running approvals, business users should not depend on Power Automate run history. Store current approver, due date and business state in the process data.
- current approver
- due date
- business status
- SLA dashboard
5. Separate business timeout from technical failure
No response from an approver needs business escalation. Connector or API failure needs technical retry and alerting. Treating both the same makes support difficult.
- business timeout
- technical retry
- error queue
- support alert