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 / Single List Change wit...
Power Automate
Unanswered

Single List Change with Attachments - Multiple Unwanted Triggers

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

I have a flow that gets triggered when a list item gets created or modified. The flow is relatively simple, sending a notification email out to a filtered list of recipients. So far, so good.

 

The problem arises when the list item has attachments. The flow is being triggered once for the list item creation, and then once again for each list item attachment.

 

I tried inserting a 2 minute delay in the beginning of the flow to allow for the attachment uploads to complete. This does not help as the triggers just queue up. I could make the flow run only on creation, but would lose the notifications when the item is modified.

 

Any ideas?

Categories:
I have the same question (0)
  • v-yuazh-msft Profile Picture
    Microsoft Employee on at
  • v-yuazh-msft Profile Picture
    Microsoft Employee on at

    Hi @Anonymous,

     

    Have you create the item first,and then add attachments to the item?

     

    If you don't want the flow to be triggered when you add the attachment,

    the only way should be you save the attachment in a same root before you create the item , and then you could add the attachment before you first save the item as screenshot below:

    Capture.PNG 

     

     

    Please let me know if your problem could be solved.

     

     

    Best regards,

    Alice

     

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Thank you - uploading the attachments first, then linking to them would probably solve the triggers, but would make the process more difficult. I'm trying an approach where I use a periodic trigger on the workflow that looks at a timestamp on each item to decide if a notifcation should be sent, rather than trigger on create/modify. That seems to work. 

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 60 Super User 2026 Season 1

#2
Haque Profile Picture

Haque 54

#3
Expiscornovus Profile Picture

Expiscornovus 47 Most Valuable Professional

Last 30 days Overall leaderboard