To what extent are "Wait For Condition" actions monitored?

[bonsai]

I have created a flow that implements "Wait For Condition."
This flow is executed about 50 times a day, and all flows are in a wait state.
The next day, the wait release conditions are met and the flows are processed.

I feel that having around 50 flows in a wait state continuing for a day may be affecting ServiceNow's performance.

Does "Wait For Condition" constantly monitor records?
It would be fine if the monitoring frequency was low, but it would be scary if it was monitoring once every few seconds to milliseconds.
Will this work when updated like a business rule with a record update trigger?

[NagaChandaE]

Hi @bonsai ,

Monitoring Mechanism

The activity registers a "record watcher" (visible in sys_rw_action table) that triggers evaluation only when the target record is updated via database commits, such as through business rules, UI actions, or scripts. It checks the specified condition at that moment, resuming the flow if met. This avoids continuous monitoring, making it efficient even for 50 daily waits spanning a day.

[Ankur Bawiskar]

@bonsai 

yes this will cause performance impact in PROD since the table data could be huge.

You can use after update BR and make your BR trigger when that wait condition is met i.e. some field get updated etc

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏