Triggered for an item on a sharepoint list, it updates some column info in the list, and moves a corresponding Folder into an adjacent Folder called "Closed". The rest of it works as expected without errors, the Folder even gets "moved" as expected with metadata intact. The trouble is the original folder is still there left behind, with all content inside of it as if it had never been moved. I figure this must be an obscure bug, but I cannot figure out what is causing it.
So after the flow is run on 1027 it looks like this:
Source Folder:
Destination Folder ("Closed"):
The Folder was "moved" (Contents inside as well) but is still completely replicated in the source folder, and the problem occurs for all of the ~20 items I have run it on.
And here is the flow action: