Business Rule firing twice on RITM update when in On Hold state

[P Seth]

1. i have a workflow in which if the On Hold target date is passed, the comment is updated in RITM using Set value in Workflow also state is set to WIP  and BR ( before) sets RITM state is set to Work in Progress if user updates the RITM during on Hold state.

2. i have another BR - after {insert and update} ( ex Name :- Comment update)  in which if additional comment changes it triggers the event and Notification is Sent to Assignee ( assigned_to)

BRs and Workflow is working fine, the issue arises when the RITM is on Hold and user updates that or Pending Target date gets passed . 

-- > If user updates the RITM during On Hold State -> The state changes to WIP and BR : Comment update runs Twice  tough the conditions of BR is : "current.assigned_to != gs.getUserID() && current.comments.changes()"

and notification email gets sent twice to asignee. 

i am not able to get it why my same BR is running twice , it should only run once.

[GlideFather]

Hi @P Seth,

have you add some logs to the BR? To verify whether it is a single BR triggered twice or another BR in parallel...

[P Seth]

Yeah i added logs to the BR and post checking logs i came accross that same BR is running twice

[Ankur Bawiskar · Accepted solution]

@P Seth 

share both the BR conditions, scripts screenshots and also the workflow step screenshot

Your Business Rule runs twice because both the user update and the workflow’s automatic update change the RITM record, triggering the rule each time. The condition current.comments.changes() is true for both updates, causing duplicate notifications.

How to fix

-> Add a flag field (e.g., u_notification_sent) to track if notification was already sent and skip on subsequent updates.

-> Check update context to send notifications only when updates come from actual users (exclude system or workflow updates).

-> Refine BR conditions to exclude workflow-triggered updates or states.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[P Seth]

BR ( before ) working fine	

current.u_pending_target_date = '';
		current.u_substate = '';
		current.state = 2;