After saving your changes those notification events should terminate and you should see that number go down when you run that query again. You may have to wait a few cycles for the notification server to catch up if there is an excessive number in that table already.
If notification definition/ rule changed after notification events got created, it might not get updated and the repeated notification event does not terminate based on the new rule . This caused many repeating entries in ns log even though it satisfies the updated termination rule for example when State is Equal to COMPLETED. The following entry should not get triggered and the event should be removed from the notification events table.
It's the same rule as the first notification, minus the current user clause. Next, you edit the Escalation tab and enter a termination rule . This is the rule that stops the escalation (sending an email to the manager) from happening.
