Unfortunately, there is no way to turn this behaviour off. It is discussed here on Trailblazer community

At CloudFiles, we're working to handle this better, so we avoid running CloudFiles actions multiple times in this situation. A workaround for now is to test the flows thoroughly before activating in production, so the failure chances are minimized.