Incorrect condition on a business rule firing the event may send multiple notificationsDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Incorrect condition on a business rule firing the event may send multiple notifications Release Any supported release Cause Incorrect condition on the business rule (which fires the event specified on the Notification). Resolution [code]When there is a Notification defined to run when a specific event is fired.And the business rule which fire the event has an incorrect condition specified, it will skip that condition and evaluate the remaining if any.This may lead to sent out multiple necessary Notifications.Ex:If there is a Business rule on "sys_history_set" with an Advanced Condition: !current.id.demand_manager.changes() && (current.updated != previous.updates)Notice the 2nd part of the condition, it has current.updated != previous.updatesThere is no "updated" field on the "sys_history_set" table.It should be current.updates != previous.updates.