What impact does Flow "For every update" trigger have on Instance performance

[Kevin Parker]

We have a flow that has been created by a consultant to manage chases for On Hold tickets. This doesn't work properly unless I amend the Run Trigger to "For every update". I am looking to get an understanding of how this could affect Instance performance? Is this a "no-no"?

These are the Triggers currently applied.

[Mark Roethof]

Hi there,

Don't see your image unfortunately.

Anyway, the run trigger is completely up to you and your business requirement. Depending on your flow, sure it can have performance impact. Though what are you after?

For example, the flow might create tasks, approvals, for a certain record. Then I would assume you don't want to have this on every update! Not because of performance... because of data.
Though your flow might also have completely other logic, and does require to run every update. So it's really up to your requirement.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020-2022 ServiceNow Community MVP
2020-2022 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[Kevin Parker]

Thanks Mark, not sure what I did there then?!

The Trigger is checking to see if an Incident is On Hold, Awaiting Caller with a couple of exclusions for Assignment Group and User of Guest. The problem with the flow at the moment is that it runs once, so it will stop when the conditions are no longer met and then fail to start again if the conditions change back to ones that should trigger the flow.

I have tested the Every Update in our Non Prod instance and it works a treat, but I am not sure how this would affect performance when pushed into an instance with a couple of thousand active incidents?