When a job executes and there is issue with Login object or perhaps some other issue, jobs end with return code 0 (but the error is FAULT_OTHER - Start impossible which in the Automic doco is meant to be return code 1820 ). In the jobs we have runtime tab "Definition for ENDED_OK if not 0 then execute a Notification.
However, under the fault condition the job still gets return code 0 so Notification is not executed.
Can you please describe a method we could implement, maybe a post process tab that would alter the return code so that the job can consider the runtime tabs definition for ENDED_OK being greater than 0 when a FAULT_OTHER error occurs.
Recently we had issue with accounts being locked and many jobs were failing FAULT_OTHER but no Notification was executed. When inspecting the job output details they get return code 0 but job is not successful.
Object name DOPSSUPUC4J005
Activation 4/11/2016 3:09:50 PM
End 4/11/2016 3:09:50 PM
Status FAULT_OTHER - Start impossible. Other error.
Return code 0
Last message U00011167 Could not find Login object '' for Job 'DOPSSUPUC4J005' (RunID '0001353254').
There are several ways to do this. The most common is to use the postconditions of the task in the workflow: