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 / SharePoint Trigger Ret...
Power Automate
Answered

SharePoint Trigger Returns Cached File Names - Always Returns First File Name

(0) ShareShare
ReportReport
Posted on by 2
Hello,

I'm experiencing a serious caching issue with the SharePoint "When a file is created (properties only)" trigger in Power Automate.

**Problem:**
When multiple files are uploaded to a SharePoint folder, the trigger always returns the filename of the FIRST file uploaded by me, regardless of which file actually triggered the flow.

**Example:**
1. I upload "FileA.jpg" → Flow runs → Registers "FileA.jpg" ✅ Correct
2. I upload "FileB.jpg" → Flow runs → Registers "FileA.jpg" ❌ Wrong (should be FileB.jpg)
3. Another user uploads "FileC.jpg" → Flow runs → Registers "FileA.jpg" ❌ Wrong
4. I upload "FileD.jpg" → Flow runs → Registers "FileA.jpg" ❌ Wrong

**What I've tried:**
- Deleted and recreated the flow multiple times
- Deleted and recreated the SharePoint connection
- Changed from split-on enabled to disabled
- Verified trigger output in run history - the trigger itself returns cached data
- The issue persists across different files and different users

**Environment:**
- Trigger: "When a file is created (properties only)"
- SharePoint: Online
- Folder path: /Shared Documents/MyFolder/Scans
- Polling interval: 1 minute
- Split On: Enabled

**Trigger Output (showing cached data):**
The trigger's `{FilenameWithExtension}` always shows "FileA.jpg" even when different files are uploaded.

**Question:**
Is this a known bug with SharePoint triggers? How can I clear this cache or work around this issue?

Any help would be greatly appreciated!

Thank you.
Categories:
I have the same question (0)
  • Verified answer
    David_MA Profile Picture
    14,956 Super User 2026 Season 1 on at
    You will want to consider the ramifications of doing this, but this should resolve the problem you are having. In your trigger, turn on concurrency control and set it to 1. This way, only one instance of the flow can run at a time. It is designed for this type of issue. But note, once you turn this on in the flow, it cannot be changed. Here is some more information on this setting: Pros and Cons of Concurrency Control in Power Automate Flows - CRM Software Blog | Dynamics 365.

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