Share via

Power Automate Workflow Lifetime limit increasing when?

Floris Swanepoel 0 Reputation points
2026-06-15T10:16:09.16+00:00

Is there an updated roadmap or ETA for increasing the Power Automate workflow lifetime limit beyond 30 days (as previously discussed by Microsoft reps)?

Microsoft 365 and Office | Development | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vergil-V 15,110 Reputation points Microsoft External Staff Moderator
    2026-06-15T10:54:28.7966667+00:00

    Hi Floris Swanepoel

    First of all, I would recommend reviewing the response from the AI, as it aligns with my findings that there is currently no active roadmap referencing a 30-day limit. 

    For your own verification, you may check the Microsoft 365 Roadmap here: Microsoft 365 Roadmap | Microsoft 365 

    If you are exploring possible workarounds that can be applied in a production environment, I would strongly encourage reaching out to the following community: Find Answers | Microsoft Power Platform Community 

    This is an active platform where experienced members regularly share their knowledge and practical guidance based on similar scenarios and deeper domain expertise. 

    I hope this provides additional clarity. 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-15T10:16:24.6233333+00:00

    There is no published roadmap or ETA for a general increase of the standard 30‑day run duration limit for Power Automate cloud flows.

    Current documented behavior:

    • Standard cloud flow run duration is limited to 30 days. After 30 days, any pending steps (including approvals) time out.
    • This 30‑day limit is confirmed in the current limits documentation under “Run duration”.
    • For long‑running scenarios, Microsoft provides specific alternatives rather than a global increase of the limit:
      • Long‑lived approvals using approvals stored in Dataverse (Common Data Service). These allow acting on approval responses even after the original flow run times out, by using one flow to send the approval and another to process the response based on Create an approval (v2).
      • Flows built on Dataverse using the Common Data Service (current environment) connector and built‑in actions only can have runs that last up to one year.
      • For SharePoint migration scenarios, guidance recommends designing flows to be re‑entrant (for example, having a flow call itself) to work around the 30‑day limit.

    The provided documentation does not state any upcoming change, roadmap item, or ETA for increasing the default 30‑day lifetime beyond these specialized patterns.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.