ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

When cancelling an Informatica Job within Automic, status can return ENDED_NOT_OK instead of ENDED_CANCEL


Article ID: 87593


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :

If you cancel an Informatica job from within Automic, there is inconsistent behavior in the status the job will end in:

If you cancel the Informatica workflow before it creates "Sessions" in Informatica, you will receive ENDED_CANCEL 
If you cancel the Informatica workflow after it creates "Sessions" in Informatica, you will receive ENDED_NOT_OK

This can affect internal auditing as these jobs should all be in an ENDED_CANCEL status. 


Cause type:
Root Cause: Depending on the timing, Informatica reports back a different status that is not consistently interpeted.


Release: AOMVMW99000-4.0-Automic-Operations Manager-VMware vCenter Agent


This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
RA Informatica 4.0.3 - Available

Additional Information

Workaround :
Use a filter object and check the LOG (Logging) for 'initiated CANCEL for' and set the remote status to 'ENDED_CANCEL - manually canceled'.