Issue | Description |
|---|---|
DBMI-28633 | When you try to stop a database or application ingestion and replication job that is already in a stopped state because of the API endpoint POST request /dbmi/public/api/v2/job/stop, the API incorrectly returns a 404 status code with the error message "JOB_IS_NOT_ACTIVE". Instead, the API should return a 409 status code to indicate a conflict. (April 2026) |
DBMI-26372 | When you view details of an application ingestion and replication job or a database ingestion and replication job from Monitor, the overall job status might be missing from the job details page. (October 2025) |
DBMI-20617 | If you select a primary cloud data warehouse from the Data Integration Home page and then start the Data Ingestion and Replication wizard from the New option in the navigation bar to create a task, the primary cloud data warehouse is not automatically selected on the Destination page. You have to select it again on that page. Workaround: None. (July 2025) |