Job Execute Batch Jobs

Purpose

The active, configurable job executes a defined queue of other Webdesk jobs one after another.

Stop on first error (stopOnFailure): If activated, execution ends with a job exception at the first failed job. If deactivated, the remaining jobs in the queue continue to be executed.
Jobs: An existing job is selected per row via the repeater. The order of the rows is the execution order.
The selected job UIDs are read from the configuration and loaded via the job service during the run.

The job logs the entire queue.
Each configured job is executed via the normal PoJobRunner with its own configuration.
After successful completion, the next job is started.
In the event of an error, depending on stopOnFailure, the run is aborted or continues with the next entry. Jobs that were not started are reported in the log.
If the batch run is interrupted by a system administrator, processing stops and the jobs that have not yet been started are logged.

Plan the order according to functional dependencies, for example import before cache refresh.
A batch configuration does not replace the individual configuration of the jobs it contains.
After the run, check the job log for started, successful, failed and non-started jobs.