During alerting event processing, the system inserts alerting events and converts them into alerts. If alerting events are still being added to the database when an attempt is made to convert them into alerts, the following error messages might appear in the svi-alert-service log:

2025-02-19T12:03:20.904Z ERROR [           ] [umerExecutor-10] .fcs.tdc.services.AlertGenerationService : Alerting event processing exception - Alerting Event ID: f42c1f34-95e2-0143-a607-f44d4e7c8639
com.sas.fcs.tdc.exceptions.TDCNotFoundException: Alerting Event not found: f42c1f34-95e2-0143-a607-f44d4e7c8639
    at com.sas.fcs.tdc.services.AlertGenerationService.process
    (AlertGenerationService.java:151)

The system then retries to convert the alerting events to alerts until the maximum number of retries is reached.

After you install the hot fix, the alerting event processing exception is set at the DEBUG level until the maximum number of retries has been reached. After that, it is set at the ERROR level. DEBUG level messages can be safely ignored.