You’re offline. This is a read only version of the page.
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?
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.
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:
Please let me know if your problem could be solved.
Best regards,
Alice
Share
Report
All responses (
Answers (
145,422
