Symptoms

If a Job Control Action targets a specific step, and the job that owns that Action is copied/duplicated, the Action may not work correctly in the new copy of the job.

More Information

A Job Control Action that targets a specific step may not have the correct setting after its owning job is duplicated, under the following circumstances:

1. If the Action targets a step in the same job that owns the Action (i.e., runs another step in the same job), after the job is duplicated the Action in the new copy points to the step in the original job rather than the step in the copy.

2. If the Action targets a step in another job, and both jobs are copied as part of a Duplicate Group operation in the Console, the Action in the new copy points to the step in the original job rather than the step in the copy.

In both cases, this produces the following results:

  • When you edit the Action in the Console, the action will show that it is going to run the job from the beginning, rather than from the step you specified.
  • When the Action is executed, the target job will not be run at all. adTempus may log an error message to the diagnostic log.

Note: This issue only affects Job Control Actions that target a specific step. Actions that run a job from the beginning are not affected.

Workaround

To work around this issue you must edit the new job in the Console and select the proper target step.

Identifying Affected Actions

We have created a script that will review all Job Control Actions on your server and list those that have invalid references.

To run this script you first need to install the third-party LINQPad program as discussed in article K00000533. You only need to install the software; you do not need to follow the steps under "Configuring LINQPad." LINQPad can be installed on the adTempus server or on any other computer where you have the adTempus Console installed.

Then download the Find invalid Job Control Actions.linq script file and open it in LINQPad.

If you have installed LINQPad on a computer other than the adTempus server, edit line 4 of the script to set the correct server name.

Use the Query > Execute command to run the script. The Results panel will list any invalid Job Control Actions that are found.

Status

  • adTempus 4
    This issue has been resolved. Resolved in version 4.4.