Incident created from the Third Party Tool  Integration, sometimes generate  error 302 entry is not exist in database, rolling back the entire transaction

This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

TAD_pollingEscalation qualification was: 

SLM:EventSchedule:TAD_PollingEscalation 
Qualification:- ('SLA_Time Scheduled' <= $TIMESTAMP$) AND ('SLA_Rule Event Occurred' = "No") AND ('BRE_TAD Event Status' = "Active") AND ('SLA_Rule Event ID' != "Update SLM:SLAComplianceHistory") AND ('SLA_Rule Event ID' != "Update SLM:SLACompliance_LastSLACalc") AND ('SLA_Rule Event ID' != "Invalidate SLM:Measurement") 

Changed it to 

SLM:EventSchedule:TAD_PollingEscalation 
Qualification:- ('SLA_Time Scheduled' <= $TIMESTAMP$) AND ('SLA_Rule Event Occurred' = "No") AND ('BRE_TAD Event Status' = "Active") AND ('SLA_Rule Event ID' != "Update SLM:SLAComplianceHistory") AND ('SLA_Rule Event ID' != "Update SLM:SLACompliance_LastSLACalc") AND ('SLA_Rule Event ID' != "Invalidate SLM:Measurement") AND ('Create Date' < ($TIMESTAMP$ - (2 * 60))) 

The only change we did is we added AND ('Create Date' < ($TIMESTAMP$ - (2 * 60))) 
This change will ensure that the SLM:EventSchedule records that are at least 2 min old will be processed by SLM:EventSchedule:TAD_PollingEscalation.