OverviewHistorical Jobs is an Enterprise Feature that allows users, through their task history, to view exactly how a job was set up at the time of running.
To begin, browse to the Task History via the main Project Menu.
As illustrated above, previously-run tasks will be listed in the Task History. Each of the jobs used in these tasks is recorded exactly as they were at the time of running. This includes the jobs exact layout (including notes) along with component properties and their configurations.
To view a task's job, click the tape icon to the right of the job.
FeaturesFor the sake of an example, we will check the Historical Jobs for the failed task (ID 142). Below we can see the Historical Jobs panel with a list of jobs on the left and the respective canvas on the right. Note that in spite of this task including a Transformation job (visible in the bottom-right of the canvas as a Run Transformation component) it does not appear in the list of jobs. This is because an error had been encountered and thus the Transformation job never actually ran in this task.
Since the job here is a snapshot to be preserved, users cannot make any changes to the canvas or the components on it. However, a component can be clicked on to reveal its exact configuration at the time of running. Here we investigate the cause of our failed job by selecting the component with errors and checking its properties, below.
From the Historical Job we have learned that the job failed because the code column wasn't recognised. We could follow the work flow back on the canvas to ensure this column has been introduced properly.
For contrast, we show a Historical Job for an earlier, successful run of the same job, below. Note now that the Transformation job dim_airports is visible in the list of jobs since it ran as part of the task.
We want to use this earlier run to remember how to fix the problem in our failed run. We view the Historical Job and go to where the code column was set up. Checking the properties for the components will reveal exactly how the code column has been set up in the working run, allowing us to fix our job with that knowledge.
It should be noted that Historical Jobs work in the same manner with Shared Jobs. When a Shared Job is run as part of a task, it will appear in the Historical Jobs view like any other component would. The only difference is that the jobs bundled into the Shared Job are given the <PackageName>,<SharedJobName>, prefix to show that those jobs are within the Shared Job in question.
Just as with normal jobs, the jobs inside a Shared Job can be clicked on to view their full layout and configuration at the time the Shared Job was run.