On October 14th, I had a list (13) of flows fail. All flows were monitoring on-premises directories for new files, over the gateway. For all the flows, the log says "There’s a problem with the flow’s trigger. Fix the trigger”. By clicking on "fix the trigger", I can see error 400, "The requested action could not be completed. Check your request parameters to make sure the path <xxx> exists on your file system..." When I edit the trigger step of the flow, browsing to the monitored folder gives the error "Error executing the api". No messages were sent to me alerting me of the failure. I discovered it accidentally, when I was expecting something that did not arrive.
I have had this problem before. If I'm not mistaken, the instructions were to rebuild the trigger. Since it is the trigger, I think this requires that I rebuild the entire flow. Having to rebuild the entire suite of flows every time this error occurs is not reasonable.
Another similar thread on this board has been open since July and no solutions have been provided. I don't think this community has the attention of the engineers.
We are just starting to build this system of monitoring and reporting components, and if this behavior and recover process can be expected from time to time, I have to question whether the use of Flow is an acceptable solution.
Can someone reassure me that there is a way to resolve these issues? Help, please!
