Recently a new set of triggers was added to the Power Automate SharePoint connector as I described in When a file or item is deleted triggers post.
When a file is created or modified extensions
I did not realize that the When a file is created or modified (properties only) trigger was also extended. Until I noticed some flows reporting the following error:
The Failure summary shows a “file XYZ doesn’t exist”. How can a file be modified and then not exist:
When I checked the site I noticed that these files were deleted and this is now seen as a modification to the file. I’#m not sure if this is a bug or not, but it is quite an annoying one.
- I will have to update my flow to check if the file that is modified actually exist
- I will now get more unnecessary runs of my flow
- The When a file is created or modified (properties only) trigger should be renamed as this is confusing
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com