Power Automate Approvals marked as abandoned in Dataverse after timeout

(0) Share

Report

Posted on by MC-24060948-0

Hi everyone,

I have a question regarding Power Automate approvals and how they behave over time.

I currently have a flow that generates an approval request. As far as I understand, if no response is provided within approximately 28–30 days, the flow times out and is terminated. In addition to that, the approval record in Dataverse is marked as "abandoned."

My requirement is different: I would like the approval request to remain actionable even after a long period of time. For example, I would like an approver to still be able to approve the request after 40 days (or even longer), even if the original flow run has already timed out.

Is there any way to prevent approval requests from being marked as abandoned in Dataverse due to time limits? Or any recommended workaround to allow late approvals beyond the default timeout behavior?

Thanks in advance for your help!

Categories:

Translation quality feedback

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

chiaraalina 2,498 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @MC-24060948-0

No, this is not possible with the standard Power Automate approvals.

A flow run has a hard 30‑day limit, and once it times out the approval is marked as abandoned. This behavior cannot be changed.

A common workaround is to redesign the flow so that approval creation and approval processing are separated, allowing approvals to be completed after 30 days. One example is described here: https://www.matthewdevaney.com/extend-a-power-automate-approval-over-the-30-day-limit/

Hope it helps!

Was this reply helpful? Yes No
Suggested answer

David_MA 15,273 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
From my understanding you want to do an infinite period of time for an approval. This is possible, but it is a bit tricky and requires premium actions, so you need the Power Automate Premium license. You need to do this:

Use the Create an approval action and not the Create and wait for an approval action.

After the approval is created, Update the Source field in the approval that was created with a unique identifier. I use the GUID of the workflow that creates the approval.

In your SharePoint list, create a single line of text field to store the approval ID. Once the approval is created, populate this field with the approval ID from the Create an approval action.

Then be sure to let the flow end.

Create another flow with the Dataverse trigger When a rows is added, modified or deleted and configure it like this:

The redacted part is the unique value that you set as the source in the workflow that sends the approval, which is the workflow ID of the sending workflow in my instance.

Filter rows value: msdyn_flow_approval_source eq 'unique_source_id' and statuscode eq 192350004

This way, the flow will only trigger when a row with this unique identifier has been modified or deleted.

Then to get the details of the approval outcome, use a Dataverse List rows action with a filter to get the row that triggered the flow.

The Approval value comes from the trigger and is the approval ID.

Then use a Get items action with a query filter to get the item with the approval ID of the item that triggered the flow (refer to step three for what I mean).

Because you are using a get items action, it will put the next steps into an apply to each, but you should only get one row return especially if you set the top count to 1.

From here, you can process the steps as you normally would except the approval outcome will be in the trigger, and the comments, etc. will be from the Dataverse list rows action instead of the Create and wait for an approval.

Was this reply helpful? Yes No