- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 04:40 AM
I have a flow which gets triggered on the update of a record(change of "state" field from "new" to the value "assess").If the record is again updated from "new" to "assess" the flow is not getting retriggered.
Solved! Go to Solution.
- Labels:
-
flow designer
-
Workflow

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 04:53 AM
Hi
As Kieran answered, you can decide, if the flow fires multiple times.
BUT: take care, that multiple fired flows on the same record do not lead to unexpected behavior.
Maybe in that case, you should think about using a business rule, instead of firing your flow several times.
This may lead you to a much clearer and cleaner implementation of your solution.
Let me know if that helped to solve your issue and mark my answer as correct/helpful.
BR
Dirk

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 04:45 AM
Hi Dinesh,
By default, a flow will only trigger the first time the conditions are met of the trigger. To change this, select your trigger and change the option that meets your needs.
Mark ✅ Correct if this solves your issue and also mark Helpful if you find my response helped with your question so other users can find it.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 05:08 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 05:32 AM
Apologies Dinesh,
The 'for every update' is only an option in Orlando

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 04:53 AM
Hi
As Kieran answered, you can decide, if the flow fires multiple times.
BUT: take care, that multiple fired flows on the same record do not lead to unexpected behavior.
Maybe in that case, you should think about using a business rule, instead of firing your flow several times.
This may lead you to a much clearer and cleaner implementation of your solution.
Let me know if that helped to solve your issue and mark my answer as correct/helpful.
BR
Dirk