Skip to content
Wall-mounted workshop trays with a teal folder and an orange tag.
Automation3 min readNovember 19, 2026

What to do when a purchase approval gets stuck in Power Automate

D
Written by
Daillac
Contents
A plant supervisor requests a spare part on Monday. By Wednesday, procurement still sees “Pending.” The finance manager is travelling and the person who could cover for them cannot see the request. To work through that situation in Power Automate, procurement needs a record of the request, the approval rule and the next action due.

Give each request a record people can open

In a SharePoint list or purchasing system, keep an identifier, the submitted version, the amount, the assigned approvers and the next deadline. The requester and procurement team can then check the status without relying on flow history or email. Restrict access according to each person’s role.
Use states that reflect the work. Pending can mean a person still owes a decision. Approved means the decision was made. Order created records a separate action that another team might carry out. If purchase order creation fails, the approved request stays visible and can be resumed.

Decide who signs off and when to send a reminder

Start with the purchasing policy. A request over an internal threshold may need agreement from both the budget owner and finance. Microsoft documents an approval mode in which all assigned people must approve and one rejection can conclude the request. The purchasing team should agree on what happens after a refusal, an absence or a request for changes.
A pilot rule could send a reminder after one working day and escalate to procurement after two. Confirm the timing and holiday coverage before automating it. If delegation is allowed, record who took over and when. Microsoft documents a 30-day maximum cloud flow run duration, including time spent waiting for approvals. If a process can run longer, keep the request state independently and design a way to resume from it.

Send reminders without reopening finished work

A scheduled flow can identify open requests nearing their deadline. Before it sends a reminder, read the current status again and check whether a reminder at that level already exists. A decision that arrived seconds earlier should prevent the follow-up. For substantial purchases, the record should also identify the rule and the version that were approved.
If the amount or supplier changes after sign-off, apply the change policy. It may require a fresh approval. When creating the purchase order, keep the request reference with it so that anyone retrying after an error can avoid creating a second order.

Rehearse the situations that hold up procurement

Ask the team to run four scenarios. The owner is away. A notification fails. The amount changes after sign-off. The purchasing system refuses to create an order. For each one, someone should be able to locate the record, identify the person who can act and resume the right step.
TablePurchase approval test cases and evidence to look for · shareable block
Purchase approval test cases and evidence to look for
Expected actionEvidence in the record
Approver absentApply the delegation rule or escalate to the assigned owner.Replacement’s name and deadline for the next decision.
Notification failedResume follow-up from the open purchase request.Request is visible, the reminder is recorded and a decision is still due.
Amount changedApply the reapproval rule to the new version.Original decision and the version it applied to.
Purchase order creation failedRetry with the original request identifier.Approval is preserved and the request yields a single order.
If an agent can submit a purchase request, apply permissions and approvals by action before giving it access to the purchasing system.
Daillac can help map the workflow and decide where the log, status and recovery rules belong. A recent request that needed manual follow-up is enough to get the discussion started.

Frequently asked questions

Can a Power Automate approval stay open indefinitely?+
Microsoft documents a 30-day maximum for a cloud flow run. For a longer request, store its status independently and design a way to resume it.
Who follows up on a pending request?+
Assign one owner and agree on when the requester can ask them to intervene. Record the follow-up with the request.
What if an approver is away?+
Follow the delegation rule in your purchasing policy. Record who made the decision and which role gave them authority to do it.
What happens if purchase order creation fails after approval?+
Keep the approval and request record. Retry creation using the request reference and first verify that a purchase order does not already exist.
D
Written by
Daillac