Two of my flows started failing with the error in the title. Both flows used to work fine . I've created a new test list/ flow and tried the update item action - that worked just fine. On the same test list I've tried adding a specific managed metadata field that exists in the "problematic" lists and now the problem returned. Any thoughts?
Solved! Go to Solution.
I am encountering the same error since today 7 a.m. CEST with several flow that run through without problems for months.
Is there a problem with taxonomiy service?
I've done some further testing with a very simple flow.
This flow is triggered manually gets a particular item and updates it .. as you can see it fails, the list has a managed metadata field called "Deal Name".
However if I click on the update item and select "Advanced Options" and select a view that does not include the managed metadata "Deal Name" field ...
And run the flow again... then it runs just fine.
This looks like a bug to me .
I think I have a temporary workaround , I logged on to the Flow Admin Centre (https://admin.flow.microsoft.com) and created a new flow environment (in the UK region - not sure if it matters). I then manually exported all my flows as packages and imported on the new environment.
It's a painful process because all the connections need to be recreated but at least the flows now work.
Thanks for your reply. Changing the view to a view with non MMD columns works (Delete step and create an new one andselect view without MMD field) but I want to modify some MMD fields in a list with Flow?
I thought this was possible?
Awesome, that workaround:
Have you previously tested with a mmd field in this step? If so, you have to delete the current step and add it again.
worked perfectly. Thanks.
Lets await a final fix.
We checked with the Product team. The issue is escalated and is being treated with high severity.
The fix would be available in the next couple of days.
We would keep you updated.
We are having the same issue. I followed the steps to create a view without MMD, deleted the step in the flow and added same one again with the new "flow view" and it worked. Waiting for an update on the issue.
Our site is on the European servers I work from the US and yesterday my time afternoon/evening hours I had issues with connections in flow.
My FLOW's are also experiencing the same issue. My client has escalated to Microsoft. The workaround works for me as well. However this I also have a Create Item action and cannot workaround this as there are MMD fields in the create that needs to be mapped.
Hopefully this will get fixed soon.
The Product team has deployed the fix.
This issue is resolved now, please check on your end and mark it as resolved if there are no issues.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!