Page History

...

The order will now go move through both nodes of the job chain. On the second node, an error will occur. If the email settings of your JobScheduler are configured correctly, you will now receive an error mail.

Notice Click on the second node job (samples/shell_error/simple_chained_job2, colored red) to open the Job pane. Note that the job state of the second job is now stopped. This means that the job will no longer process any orders. The order simple_error_order is now enqueued before the job. Other orders running into this job will also be enqueued.

• (optional) open the job chain menu (right click over the 'simple_error_chain' chain) and choose add order (leave everything empty) to add another order to the job chain which will also be enqueued at the second job.
• (optional) click on the job and choose unstop from the job menu which will appear on the right side of the interface. This will cause the job to retry processing the orders but as the error remains, the job will be stopped again.
• Edit the job configuration file simple_chained_job2.job.xml
  (Edit the file by either opening it in a code editor or using JOE - JobScheduler Object Editor.  Note that the job configuration can be read in JOC - but not edited - by opening the job context menu and selecting Show configuration. )

• Change the change exit 5 (which caused the error) to exit 0 and save the change.

Once the JobScheduler has noticed the change in the configuration file, it will update the job definition and unstop the job automatically. The order(s) will then be able to run successfully through the job.

...