Incorrect condition in a business rule firing the event may send multiple notificationsIssue <!-- 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; } --> Incorrect condition on the business rule which fires the event specified on the email notification may send duplicates. CauseWhen there is an email notification defined to run when a specific event is fired, and the business rule which fires the event has an incorrect condition specified, it will skip that condition and evaluate the remaining, if any. This may lead to send out multiple notifications.ResolutionIn a use case example where there is a Business Rule on the [sys_history_set] table with the Advanced Condition:!current.id.demand_manager.changes() && (current.updated != previous.updates)Notice the second part of the condition which has:current.updated != previous.updatesThere is no "updated" field in the "sys_history_set" table. The correct statement should be:current.updates != previous.updates