Lost failure mesages from scheduled instances

Question

We've found that when reports are scheduled with the "Cleanup instance after schedule", or with an Instance Limit, failed instances are removed as well as successful instances. 
In trying to find the actual reason for the failures, I checked the audit tables.  But the only indication of the failure there is an ERROR_CODE value of 1.
Is there a better way to identify failed instances, and the actual reason for the failure?

Answer 1

Hi Joe,
Typically you would need to enable tracing of the XI3.1 Job Servers in order to get more detailed information on the schedule failure.
There is also sometimes information in the Application Event Server logs - might be worth checking on the XI3.1 server.
In terms of the schedule values which are submitted back to the CMS from the Job Server the values are:
3 - The job failed. Use error message or outcome to get more information.
8 - The job is paused. Even if all dependencies are satisfied, it will not run.
9 - The job has not started because dependencies are not satisfied. Dependencies include time constraints and events
0 - The job is currently being processed by the job server.
1 - The job completed successfully.
These values could be queried by the Query Builder.
I'm not aware of what the ERROR_CODE = 1 value represents, but if I were you I would try and see via the tracing if there's a pattern to the schedule failures - most likely you can tweak the job\report server settings or modify the report(s) to rpevent these schedule failures.
I hope it helps.
Kind regards,
John