Job Details - Run(s) Tab (AutoSys/CA7)

Note: In the event that there are multiple runs for the job in the jobstream run, the runs will be displayed side by side. For example, if there were two failures and one success, you would see each run displayed side by side in the Runs tab.

The properties dialog tab displays the following job run properties which can vary depending on the schedular type:

Critical Path: Indicates if the selected job was in the Critical Path of this particular run.
Retrys: Usually one, this value indicates when a job has been restarted more than once due to failures or other unusual conditions.
Start Time: When the job or box (group) started.
Running Time: When the job entered Running status. Note: boxes will not have a Running Time value.
End Time: When the job or box (group) completed.
Duration: The length of time that the job was running.
Finish to Start Delay:This statistic (in HH:MM:SS format) reflects the time that passed after the jobs’ last predecessor finished and before the job started. This is included in System Delay for the jobstream as a whole. The time when job is on-hold is captured and represented in finish-to-start delay, not operational delay.
Start to Running Delay: This statistic (in HH:MM:SS format) reflects the difference between the Start Time and the Running Time for the selected job. This is also included in System Delay for the jobstream.
Designed Delay: This statistic (in HH:MM:SS format), captured only in , can reflect delays in the jobstream that are not caused by system delays, but rather are a function of how a job has been defined to the scheduler.

As an example, if a job is in a box (group), and the scheduler has a start time of 11:00 p.m., the job inside of that box would normally start immediately after the job starts. However, if the job inside the scheduler has a hard start time of 12:00 a.m., then there is a delay of 1 hour before the job inside the box starts, caused by the definition of the job. Automic Automation Intelligence reports such a time difference as Designed Delay.
Operational Delay: This statistic (in HH:MM:SS format), captured only in , reflects delays that are neither caused by the system, nor are designed into the job definition. Rather, it reflects a delay that is most likely due to an operator, or human delay. As an example, let’s say that a job fails at 1:00 a.m., and it has no restarts defined in the scheduler. An operator notices that the job has failed and manually intervenes to re-start the job at 1:10 a.m. The 10 minutes between the failure of the first run of that job and the initiation of the second run of the same job in the same run of the jobstream will be reflected as Operational Delay.
Exit Code: Exit code of the scheduler job
Run Status: Last known job status: Success, Failure, Terminated, etc.
Run Machine: The machine the job actually ran on.

Tip: You can use the Job Details Dialog in conjunction with navigation to easily spot differences between jobs as you navigate upstream and downstream. Simply bring up the Job Details Dialog, and the information will change as you navigate upstream and/or downstream.