Found this issue was due to login credetnials. In my case, I created a flow, tested it, then later added a step to create a sharepoint folder. Because the sharepoint step wasn't present when I first tested the flow, subsequent tests using the same source data failed. Once I logged out and back in and retriggered the flow from Dynamics (Using the CDS When a Record is Selected trigger), the system asked for authorization to access both Dynamics and Sharepoint and ran fine. It was this initilization before adding the steps that needed addtional security that caused the issue.
@ryanperrymba also came to the conclusions this was a credentials issue. in my case the flow was created by owner A.
I came in and made a small update to create an item as co-owner B the step kept failing due to this error. I changed the connection to be owner A and it worked fine.
@ericonline Thanks for the solution to run the flow with "I'll perform the trigger action" instead of "
Use data from previous run". That fixed it for me. It seems, "Use data from previous run" uses corrupt connection details as well.
Hi @DennisKuhn1 , It isn't that the connection data is corrup, it is that you've added additional connections / changed them, and the cached data run does not include the updated / correct connection data. If you add steps to the workflow requiring new connections, the old runs don't contain the connection info for these.
Look out for new contribution recognition badges coming SOON!
Join us for the first ever Power Platform Online Conference!
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!
Learn how to build the business apps that you need.
Find out where you can attend!
Watch & learn from the Power Automate Community Video Gallery!