RunID changed for jobs started with REST API after log change

book

Article ID: 223180

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

An issue we face is that some objects scheduled for execution in the future via REST API another RunId is created for their execution after a log change.
This behavior makes it impossible for the Client to check the result of the initially scheduled object.

Cause

The log change is needed in the case of ILM. If this was not done there would be a risk that the drop of the partition would fail.

However, during the log change for executions with ONCE the wrong field was used in the EH table.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

This will be fixed in a future version of the product.