Workflows Migrated from 9.0 to 12.0 are not automatically de-activating

book

Article ID: 195925

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation CA Automic Operations Manager CA Automic Oracle

Issue/Introduction

Workflows recently migrated from an older version (9.0) to version 12.0

These workflows require SYNC objects and have been set to SKIP for the "else" action.

The attributes tab has been set to "Automatically de-activate....after error free restart" and the error free status is "ANY_OK"

However the workflows are accruing in the Activities window with a status of "ENDED_SKIPPED - Skipped because of SYNC condition" and not de-activating (unlike they did in older versions).

When we attempt to manually de-activate we get the message "De-activation of task '{name}' not possible, because there are '{number}' active tasks inside the workflow construct remaning", however all child tasks (a mixture of JOBS, JOBP and EVNT) have the same "ENDED_SKIPPED" status.
It is necessary to do a "forced" de-activation manually.

 why these workflows are not auto de-activating.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

Please set the below option in Job Attributes to resolve the problem. 

Attachments