In short: A cloud-flow run, including a step waiting for approval, is documented as timing out after 30 days. Store the request and the decision in your own record. Do not design a loop and call the limit solved.
A pending approval is a business record. It is not only a step that happens to be waiting inside a flow. Microsoft’s limits and configuration page, checked on 8 November 2026, states that run duration is 30 days from the run’s start and includes flows with pending steps such as approvals. After 30 days, pending steps time out. The same page lists run retention in storage as 30 days from the run’s start. If a person might decide later than that, the decision has to survive the run.
This is not a general comparison of automation products. A purchase-order matrix is a different article: purchase order approval. What you keep after the run history disappears is data retention.
What the 30 days covers, and what it does not
The 30-day run limit is a platform limit on that cloud-flow run. It is not a rule about how long your company may keep an approval in SharePoint, Dataverse or an accounting system. It is also not a promise that the run history is your audit file. At 30 days the stored run can be gone even if the business decision must remain. Design the record first. Then let short-lived flows read and update it.
Microsoft also documents that turning a flow off stops new runs while in-progress runs continue, and that deleting a flow cancels in-progress and pending runs. Deleting the flow that “holds” the approval is a way to destroy the wait. It is a poor way to store the decision.
A durable record, described without a magic template
A supportable shape, which still has to be validated against the features your tenant is licensed for:
- Create a request row when the business event happens. Give it an id and a version.
- Store status, current approver, due date, the document version and, later, the decision, the actor and the time.
- Use a flow to notify, to set status, and to listen for a response. Each of those flows can finish. None of them is the archive.
- When a response arrives, ignore it unless it names the current version and the request is still open.
Do not describe a loop, a delay or a child flow as something that removes the limit. Microsoft’s page does not say that. If a supplier says their template is exempt, ask them to show the current documentation for that pattern and to demonstrate it. “Start and wait for an approval”, as in the sequential approvals tutorial, is a waiting step inside a run. It is subject to the run’s lifetime.
Expiry, reassignment, cancellation, late replies
Write the outcomes:
- Expiry. The request moves to expired or escalated. The old approval id can no longer approve it.
- Reassignment. The current approver changes. Responses from the previous approver do not count unless your policy says they do.
- Cancellation. Status becomes cancelled. A late approve is recorded as a late response and does not reopen the request.
- Revision. A new version supersedes the old. The acceptance test is an old approval link used after the revision. It must not approve the new version.
Licences and where the row sits
Power Automate licensing depends on whether the flow is covered by a user, by a seeded entitlement, or by a Process allocation, and on whether the connectors are premium. Dataverse, Approvals and custom tables are not free assumptions. The implementer should demonstrate the design in a tenant with the licences you will actually own, including the trigger that resumes a request after the original run has ended. A slide that says “Dataverse” is not that demonstration.
Recovery without a double decision
When the run times out, the request row is still pending and a person can see it. A recovery flow may remind or reassign. It must not create a second row that is also allowed to approve, and it must not post a downstream transaction twice. Tie the side effect to the version and to a “posted” flag. The same recovery rules are in the maintenance guide.
Before production, test with a shortened clock if the platform allows a realistic simulation, and also plan a real wait long enough to see a timeout in a non-production environment if you cannot simulate it honestly. Do not sign off on a five-minute demo and call the 30-day path proven. This design does not offer an unlimited run. It offers a record that is still there when the run is not.
Tests and questions
- An old approval link is used after a new version exists.
- The flow times out while the record is pending. The record is still visible and still the authority.
- A response arrives after cancellation and does not reopen the request.
Ask where state lives when no run is active, which licences the design uses, and how an expired link is rejected. Ask what happens to in-flight requests if someone deletes the flow.
Illustrative scenario, not a client engagement and not a claim that a particular template is supported: a capital purchase waits on an external board. The request row holds the version and the status. Short flows send reminders and write an authorised change. Nobody extends a single run with a loop and calls the limit avoided. The tenant’s connectors and licences are checked before the design is bought.
If nobody on staff can own that design, the hiring note is when to hire a Power Automate consultant.
To time one approval that already outlives a month, use the contact form or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
Where should approval state live if the run can die?
On a record you own: request id, version, current approver, status, due date and the decision payload. The flow may create and update that record. The record must still make sense when no flow is running.
Which licence does a durable design need?
Whatever the chosen tables, connectors and approvals require in your tenant. Microsoft distinguishes user licences from Process allocations and premium connectors. Ask for a design that has been shown to run on the licences you already have, or for the extra licences named explicitly.
How do you reject an old link after the request changes?
The link or the approval id is bound to a version. A response that names an older version is stored as rejected or ignored, and it does not move the current version to approved.
Can a delay or a loop keep one run open past 30 days?
Do not plan on it. Microsoft’s limit is on the run, including pending steps. Treat any design that claims to defeat the limit as unsupported until the vendor shows current documentation for that tenant.
