Skip to main content

Null Job

In briefA Null Job does no work. When it runs, the platform completes it on the spot and it finishes OK. It runs inside the platform, so it needs no agent, no connection and no parameters. You use it to shape a workflow, not to run anything.

WhereIn Design › Workflows, open a workflow and open the job in the Job Editor (open its context menu on the canvas › Edit Job). On the Job Definition tab, choose Null Job as the job type. The editor hides Agent Assignment and Job Parameters for this job type, because there is nothing to set.

WhenUse a Null Job when you need:

  • one point where many jobs meet, so a later job depends on that one point instead of on each of them;
  • a single starting point that several jobs can depend on;
  • a job that exists only to fire events;
  • a placeholder you control while you build a workflow in an on-hold state.

To wait for a file, use Wait for File. To run a command, use Run Command.

How

  1. Add a job to the workflow and choose Null Job as its job type.
  2. Make the jobs it should wait for its predecessors, and make it the predecessor of the jobs that come after.
  3. Add any events it should fire.
  4. Save the workflow.

For the full steps, see Use a Null Job.

Notes
  • A Null Job's start and end time are the same moment.
  • It has no failure path of its own. If one never finishes, look at what it is waiting on, not at the job.
Watch out
  • A Null Job that sits waiting is usually waiting on a dependency that has not been met. Check its predecessors before you assume something is broken.
  • One that stays on hold was probably built on hold on purpose. Release it when you are ready.
  • Before you delete a Null Job that seems to do nothing, check the workflow design. It may be what holds the dependencies together.