End action of a sync object was not executed

book

Article ID: 196135

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

We recently had a problem when using a Sync object in a job plan (JOBP). A file transfer (JOBF) has aborted within the job plan. This was repeated and the job plan ended with the status "ENDED_OK". However, the end action of the sync object was not executed.

Steps to reproduce

We have the following Jobplan

In the JOBP we have a file transfer job JOBF.EMO_P_APP1.PI3ASCS.CSV_BESTELLDATEN.PI. In the file transfer job select "Cancel transfer" if file exist in the destination.

Execute the jobplan first time and it will work correctly and transfer the file to the destination. execute the jobplan second time and this time the workflow will be blocked since the file exist at the destination

Delete the file at the destination and restart the FT job from the process monitor. This time the worflow will complete with status ENDED_OK - ended normally but the end action of the sync object was not executed.

Job report
2020-06-17 08:48:04 - U00004408 SYNC 'START' condition: All SYNC objects have successfully been reserved. Actions will be executed.
2020-06-17 08:48:04 - U00004414 SYNC object 'SYNC.PI_XLS_CSV' is changed from status 'BELEGT_FREI', value '+000000000' to status 'BELEGT_FREI', value '+000000001'.
2020-06-17 08:48:04 - U00007000 'JOBS.EMO_P_APP1.SAVE_MOVE_CSV_DATEIEN.PI' activated with RunID '0001039017'.
2020-06-17 08:48:04 - U00007000 'JOBS.EMO_P_APP1.COPY_DATSI_CSV_DATEIEN.PI' activated with RunID '0001039018'.
2020-06-17 08:48:04 - U00007000 'JOBF.EMO_P_APP1.PI3ASCS.CSV_BESTELLDATEN.PI' activated with RunID '0001039019'.
2020-06-17 08:48:04 - U00007000 'JOBS.PI3ASCS.MOVE_EMO_CSV_DATEIEN_PI' activated with RunID '0001039020'.

The impact of this is that the Jobplan will not execute the next time and will have the status "waiting for SYNC" The SYNC object needs to be manually reset each time this problem happens.

 

 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

This is a bug and will be fixed in a future release.

As a workaround, on the task JOBS.PI3ASCS.DUPL_EMO_CSV_DATEIEN_PI (the task following the FT job) in the task properties, change the "Block task and send abort signal to parent" only to "block task".

Attachments