Hi @ddelias
Sorry but I am a little confused now. Do you have a development environment where it is acting the same? Or is this just in production and nowhere else to test? In your Compose, which I am guessing its the Last Modified Date or the File in the Loop? That clearly shows the file is NOT over 15 days old, so it wouldn't be deleted.
You shared a picture of files from June before, now this list shows files from this week. You have to narrow it down and not try to solve it for all files.
Actions to Take please
1. I see that your flow has 20 iterations in the Apply to each. Click through every single one of them and look at the Compose output. See if ANY of the Last Modified dates are older than 15 days. If you find that none of them are, then it makes sense that its not doing anything.
If you still believe it SHOULD be doing something then do the following.
If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others
Cheers
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey
1. Pick a file that is older than 15 days and make sure it's the last modified time/date not created
2. Grab the name so you know what it is
3. If you are able, because the is DEV, then ad another compose where the first one is, and put the File Name in it.
4. Run the Flow
Once again, review the Run and step through each of the Iterations of Apply to Each
Review the Name of the File to verify if its the one you are debugging
If so then look at the compose of the last modified date time
If its not showing the date that should be deleted, then we have to dig further.
Right now, the most important is, can you reproduce it with a single file that SHOULD be deleted and isn't and not look at lists, thats not going to help. Narrow the debugging field a ton.