Same issue happened to our Change approval flow.
We are running ~70 approvals per week and this will create a huge impact to the process.
Hopefully this issue will be resolved soon (last time took more than a month), else there is high chance that Management will decide to stop using Flow on Company process...
@AngryBatVoice I think we have to make this topic live again...
In case it helps, since I posted about this last week, I reinstalled Office in one test laptop with an older version as suggested (Version 1908 (Build 11929.20300 Click-to-Run), but every flow approval from Outlook (desktop version, web) failed with this error. Then reverted back to v1909 (Build 12026.20264 Click-to-Run).
As a workaround, I added a message on the approval email body, telling that to approve users should go to the Approvals page in Flow (which was the only option working beside the approvals on the Flow iOS app).
Tried creating new flows, but the behavior was the same until suddenly, it started working again on its own three days after. I believe it has to do with the new Approval versions in Flow, but have no clue what happened. Frustrating.
when the mistake was the first time, I thought MS would be instructed. Now the error is the third time and no reaction ?? Should I understand that Microsoft does not have a testing team and now is testing on customers? Please replace testers and stop offering paid services as open source quality . We're really frustrated. Thank you in advance, your PAYING customer
Same issue here. Particulary frustrating as we are Building a canvas app which was working until about about 3pm GMT yesterday.
I have just spent the better part of this morning trying to figure out how I broke my flow until I stumbled upon this thread..
Same issue here and symptoms as everyone else has described! Frustrating as previous workaround was to approve via OWA which is not working either.
I'm going to test again but Approval failed via the Outlook client and OWA but a Rejection showed the same error message in Outlook but apparently went thru anyway and completed the flow correctly. Strange...
I can confirm now that since a few minutes ago; both, Approve and Reject, are working from Outlook.
I really would appreciate if Microsoft could give us a status about this "Known Issue" or a road map to the final resolution plan and/or mitigation strategy. I certainly would prefer not to have to tell my client to plan for frequent disruption of their processes every other month or so and wait for it to magically start working again.
Confirm that it's now working with Outlook.
It's true that Microsoft need to have reports on issue resolving progress & status.
Feels like users are spinning around without any idea what is going on ...
Obviously this issue has been fixed and re-broken by new versions of Outlook. For those of us in enterprise not knowing if/when this basic functionality will cease to function makes deploying a Flow solution for an organization a non-starter.
We expect more from Microsoft.
I agree that the other frustrating thing is the lake of acknowledgement by MS there there is a known issue. This diminishes confidence in the flow as a solution platform for enterprise.
My solution is now sitting waiting for these items to be fixed.
-Approve/reject via outlook email.
-Requested by listed user inaccuracy.
Microsoft please take the high road here and admit there is a problem, state what actions are being taken to resolve, and when we can expect the fixes.
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!