I am experiencing the same error with "Move or Rename a File using Path." Also started on Friday July 11 - after successfully running for over 2 years on a set of 40+ flows I use. I created a support case. You should too.
I also looked for and found post by others who have reported this issue in the past, but I did not see any responses with solutions that I could take any action on. In the most prominent one, the resolution stated, it just started working again - which implies MS fixed something on their side rather than it being a problem with the user's Flow.
I guess the silver lining is it's not just me experiencing this issue - hopefully others are reporting the issue too and it can be resolved.