This page shows details about a job.
The panel at the top includes general information about the job:
Clicking
The rest of the page shows a visualization of the job and any sub-jobs that got launched from the job along a time axis. The horizontal axis represents the time, and the vertical axis represents the job and its sub-jobs. In particular, the job itself is represented by the first row; in case there are any sub-jobs, these are shown as additional rows underneath, sorted by the time they started running.
Some apps launch several parallel sub-jobs. Often, the number of sub-jobs reflects the size of the input data or the size of a reference genome. Moreover, apps may call upon other apps which will also appear as sub-jobs. Since a sub-job itself can launch more sub-jobs, complex apps may end up generating an intricate set of sub-jobs with elaborate dependencies. The goal of this visualization is to give you a quick idea of these jobs as a whole, and the time they took to run. The rest of the text will use the term job to refer to either the job (first row) or its sub-jobs (additional rows).
Each row includes the job name, an icon describing the job status, and a bar depicting the time span of the job. This bar starts at the horizontal point when the job started running, and ends at the horizontal point when the job transitioned into the Failed, Terminated or Completed status (or at the current time, if the job is still running). This running phase may be divided into two pieces, using different colors:
If the job has failed, a red banner underneath the top panel will communicate the error reason. If a particular sub-job is responsible for the job failure, the name of that sub-job will be shown in red.