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.