I have seen others post this as well, but have not seen any under bugs.
Suddenly all our Flows are failing with this error after any file is attempted to be moved if it had ever been moved before. Our entire project is now at a halt.
Solved! Go to Solution.
Hi All,
Could you reproduce the same issue today?
I have made a test today and I still cannot reproduce the same issue.
Please check my configuration:
First Flow:
The second Flow:
Please feel free to let us know if the issue still exists.
Best Regards,
We have the same problems. We have three folders:
Ready for Internal QA
Ready for External QA
Complete
The SharePoint Move File action always fails between "Ready for External QA" and "Complete" and we receive Error Message 400: An Item with the same key has already been added.
Same error here!
Hi All,
Could you reproduce the same issue today? Please take a try again.
I have made a test and I could not reproduce the same issue on my side.
Please check my configuration and flow run history, If there is a difference from your configuration, please let me know:
I will follow this issue, please provide more details so that we could reproduce the same issue and report this issue.
Best Regards,
I was also experiencing this issue on all of my libraries and flows yesterday, it went from the the error message:
"An item with the same key has already been added. CallStack --"
to new error message this morning:
"status": 400,
"message": "Object reference not set to an instance of an object. CallStack --
This has impacted our already impacted staff significantly trying to work from home and these files are not being moved along the process. Please help.
Hi All,
Could you reproduce the same issue today?
I have made a test today and I still cannot reproduce the same issue.
Please check my configuration:
First Flow:
The second Flow:
Please feel free to let us know if the issue still exists.
Best Regards,
Mine all appear to be working again today.
I will leave this open until some of the other people who commented earlier also confirm they are no longer having this issue.
Once there is a level of comfort, I will mark this as closed.
All my Flows that were throwing this error started to function correctly sometime on April 4th. I will also continue to monitor them this week and report back.
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.