The previously deprecated failed_transaction_modification_ids and progress_percentage fields are no longer returned in the batch status response.

The Rule Schedule API provides visibility into rules execution schedule.

• POST /api/rules/schedule

The progress_percentage field in the batch status response has been marked as deprecated and will be removed in a future version.

Request and retrieve data export reports for specific dates through the Transaction Monitoring Observability API.

The failed_transaction_modification_ids field in the batch status response has been marked as deprecated and will be removed in a future version.

The response now includes reject_on_invalid and error message in the response for observability batch transaction API.

Transactions with non-unique modification IDs within a batch are marked accordingly in the validation results file, and those transactions are rejected.

reject_on_invalid configuration flag moved to request body.

Trigger the execution of set of scheduled rules for a specific date

• POST /api/rules/rerun

Each batch must contain only unique transaction modification IDs. If duplicate transaction modification IDs are detected, the entire batch will be rejected, regardless of the reject_on_invalid flag is set to either true or false.