I have an annoying situation.. I have a flow that is triggered by a new list item but i also have a flow triggered for when an existing item is modified. What is happening is everytime a flow is created, it triggers my modified flow, resulting in 2 approval emails being sent. Can anyone help with a workaround?
I am attempting to add a condition of created at time, but my syntax is not working.
Condition is as such on the modified item flow:
This is being ingnored for some reason.
You have some ways to do it:
If you need something, please contact me.
Thanks for the comment, I hadn't thought of using just the modified flow.
As far as comparing the created and modified times, this still fires off, im thinking it keep tracks of seconds, and the fact that they are produced a second apart, they trigger the flow.
Unfortunately I think we are not able to change this, I´ve searched here on flow forums and with some friends that are working with flow too but I found nothing about it.
I´ll keep searching and if reach something, I tell you ok?
I'm having exacctly the same problem.
I cannot use only the modify flow because I need to do different things when it's created and when it's modified.
I was trying to use the first suggestion of creating a new column to set if the flow was triggered but I cannot figure it out. @douglasromao Any ideas of how I could do it?
Not sure if this will help.
I use a service account to execute all of my flows, and I am the only one with access to this account. That being said, I have added a condition at the beggining of my flow verifying if the modification was done by my service account, if so, i terminate the flow.
If not, i proceed with the change.
Otherwise if my previous suggestion is no help. Have you considered running 2 different flows? I have noticed that you can now chose either when an item is created or when an item is modified as a trigger. (flow used to package these 2)
If so, just run 2 different flows and they will know when to trigger. You might want to consider using the service account check condition if you use this approach as it will surely fire off once an item is modified.
Let me know if this works! Flow needs many more improvements before it becomes a viable and easy to use solution.
Thanks a lot!
Yes I actually have 2 flows: 1 for when an item is created and 1 for when an item is modified, but it was still running both.
I am also using a service account to run the flows and previously I have tried what you mentioned but maybe I was doing it wrong.
I added a condition in my modify flow to check if the modified by account was my service account, if not continue the flow.
It is working now as expected 🙂
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!