Users of Automation Analytics & Intelligence (AAI) version 24.4.0 may encounter an error when attempting to enable or modify alert criteria for a newly created JobStream.
Failed to update alert criteria./aai/api/jobstreams/{id} returning an HTTP 400 Bad Request.jaws.log or server.log records the following exception: jakarta.ws.rs.BadRequestException: Only one default JobStreamSLA can be defined.A defect in the JobStream creation logic (addNewJobStream) causes an orphaned "default SLA" record to be persisted in the database while the in-memory cache remains empty. When a user subsequently saves a deadline (e.g., a User-Defined End Time), a second default SLA is created.
The Alerts dialog attempts to submit the entire JobStream object, including both default SLA records. This triggers a server-side validation check that prevents more than one default SLA from existing, resulting in the HTTP 400 error.
This issue is a known defect (DE203672) and is targeted to be fixed in AAI version 24.4.2.
To resolve the state for an affected JobStream without a database restart: