DX O2 batch ticketing aborts after a single ticket creation failure

Products

• DX SaaS

Issue/Introduction

When a batch of alarms is being processed for ticket creation, a single failure (such as a 400 error from the ITSM system) causes the entire batch to abort. Subsequent alarms in that polling cycle are skipped, resulting in missing tickets for valid alarms.

Environment

DX O2 SaaS

Resolution

This fix has been released in NA production as part of 24.4.1 release which happened on weekend (May-03-2026).

You can validate the fix as follows:
The fix address the issue where one ticket creation failure causing the other tickets to be not created.
Now with fix in place, if one ticket creation failure occurs, the other tickets should be created successfully.