Fixed issues

After the February 2025 upgrade, the Secure Agent Database Ingestion service might generate an excessive amount of log files at /app/infaagent/apps/Database_Ingestion/logs/services/task_container/Default, which can potentially consume all storage on disk.

For an application ingestion and replication or database ingestion and replication initial load job that fails with the target custom property writerSqlUnloadAsyncLoading set to true, the monitoring interface might incorrectly display the status of Completed.

Unload processing in application or database ingestion and replication tasks that use the initial load or combined initial and incremental load type might take a long time to complete.

When application ingestion and replication or database ingestion and replication jobs are terminated, the task units where the Secure Agent is running might not be released, which causes the number of available task units to remain static.

A duplicate instance of an application ingestion and replication job or a database ingestion and replication job might run in another agent when the original Secure Agent running the job expires and restarts the job.

If you use multiple agents in a Secure Agent group with maxTaskUnits property set to a value greater than 10, tasks might not be load-balanced equally across multiple agents.

Application ingestion and replication jobs and database ingestion and replication jobs that use the incremental load or combined load type and have a relational database target might encounter a duplicate key error on a target table if the job restarts multiple times because of a DML apply error on another target table.