web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / No processing / email ...
Power Automate
Suggested Answer

No processing / email reminders from a Zarchive folder in SP

(3) ShareShare
ReportReport
Posted on by 10
I have Zarchive folders in libraries. 
Requirement: to send email reminders 3 months after the last modification date. 
I do not want to send the reminders for files in the Zarchive folder. How to acheive this
 
Categories:
I have the same question (0)
  • Suggested answer
    SpongYe Profile Picture
    5,909 Super User 2026 Season 1 on at
    Hi @MG-30041246-0
     
    You can achieve this by adding an additional check in your flow to exclude files whose path contains the Zarchive folder.
    If you are using a scheduled Power Automate flow with Get files (properties only), first identify files where the Modified date is older than 3 months. Then add a condition before sending the reminder email.
    and(
      lessOrEquals(item()?['Modified'], addToTime(utcNow(), -3, 'Month')),
      not(contains(toLower(item()?['{Path}']), '/zarchive/'))
    )
    I recommend checking the folder path rather than the file name, because checking only for Zarchive could accidentally exclude files that simply have that word in the file name. Using /zarchive/ makes sure the match is for a folder path.
     

    If you have any questions or feedback, please let me know. Have a great day! 😊

    -----------------------
    SpongYe Power Platform Enthusiast [LinkedIn] | [Youtube| [My blog]

     

    I love to share my knowledge and learn from others. If you find my posts helpful, please give them a thumbs up 👍 or mark them as a solution ✔️. You can also check out my blog [@SpongYe] for some cool solutions and insights. Feel free to connect with me on any of the platforms above. Cheers! 🍻

  • Suggested answer
    RaghavMishra Profile Picture
    261 on at

    Hi MG-30041246-0,

    The path-based exclusion is the right pattern. If your library has more than a few hundred files, you can also push both filters down to SharePoint using the Filter Query field on Get files (properties only), which is more efficient than pulling everything and filtering in the flow.

    Option A — Filter at source with OData (recommended for larger libraries)

    1. Add Get files (properties only) (SharePoint connector). Point it at the document library.
    2. In Filter Query, combine the modified-date filter with a folder-path exclusion:
      Modified lt '@{addDays(utcNow(),-90)}' and not(substringof('/Zarchive/', FileRef))
      • FileRef is the server-relative path of the item — this is what lets you exclude an entire folder rather than matching on file names.
      • SharePoint's OData supports substringof for string contains; contains() is not supported here, which is a common gotcha.
      • The threshold view limit (default 5,000) still applies — make sure Modified and FileRef are indexed columns on the library, otherwise the call fails on large libraries.
    3. Apply to each → send the reminder email. No extra Condition needed.

    Indexing columns reference: Manage large lists and libraries.

    OData filter syntax for the SharePoint connector: SharePoint connector reference.

    Option B — In-flow Condition pattern with a small refinement

    If you stay with the in-flow Condition approach, two small tweaks help reliability:

    • Use FileRef (server-relative path) rather than the dynamic {Path} token — FileRef always includes the full library path and is the canonical SharePoint field for "where does this item live."
    • Wrap the comparison with toLower() on both sides so a renamed zArchive / ZARCHIVE folder still gets excluded:
      not(contains(toLower(item()?['FileRef']), '/zarchive/'))

    Why prefer Option A

    Microsoft's guidance for the SharePoint connector is to filter at the source whenever possible — pulling all items and then filtering in Apply to each hits connector throttling limits faster and consumes more API calls per run. See Limits and configuration in Power Automate for the per-connection throttling thresholds, and Working with large lists and libraries for the 5,000-item threshold behavior.

    One more thing worth checking: if the Zarchive folder is created by moving files there (not by archiving in place), make sure the flow's trigger or schedule runs after the move is complete — otherwise a file that's about to be archived can still hit the reminder window.

    Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

    Raghav Mishra — LinkedIn | PowerAI Labs

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard