web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Cannot revert to previ...
Power Automate
Suggested Answer

Cannot revert to previous working version

(0) ShareShare
ReportReport
Posted on by
As title states.
 
I cannot revert to a previous working version of the flow. Whenever I do try to revert it, the browser crashes. I have also tried this on the desktop version.
 
Error message that does come up when the browser does crash RESULT_CODE_HUNG. I have tried this on both with 16Gb and 32 Gb of RAM.
Categories:
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,318 Moderator on at
     
    The RESULT_CODE_HUNG error points to the browser becoming unresponsive, which typically happens when the Power Automate designer is trying to process a large or complex flow definition.

    When you revert to a previous version, the designer has to fully reload that version’s JSON and rehydrate all actions, connections, and dependencies. If the flow is large or has a long version history, this can put significant pressure on the browser and cause it to hang.
     
    (Applicable only for PAD)
    Regarding Power Automate Desktop (PAD), you’re also looking in the right direction. Versions 2.66 and 2.67 have a known issue that can leave installations in an inconsistent state, particularly affecting machine connectivity and service behavior.

    If your cloud flow includes desktop flow actions or machine references, the designer may attempt to resolve those dependencies during the revert operation. If PAD is not responding correctly, the page can end up waiting indefinitely for a response, which can contribute to the browser hang you’re seeing.
    ---

    A few things you can try:

    Isolate the browser
    Try the revert in an InPrivate/Incognito session to rule out extensions or cached scripts interfering with the designer.

    Check PAD version (only if applicable)
    If the flow uses desktop flows, avoid versions 2.66 and 2.67. Rolling back to 2.65 is currently the most stable option until 2.68 is available.

    Try alternative entry points
    If the flow is inside a Solution, try accessing version history or export/import from there. In some cases, those paths are more resilient than the main designer.
     
    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.

    Sunil Kumar Pashikanti, Moderator
    Blog:
     https://sunilpashikanti.com/posts/

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard