Run Bulk Configuration
The Run Bulk Configuration scheduler job executes an existing Bulk Configuration from the Bulk Processor module on a schedule. The configuration itself — which table to process, which work query to use, and which processing steps to apply — is defined in the Bulk Processor admin module; this scheduler job only picks one of those configurations and runs it whenever the schedule fires. Open its configuration via the Scheduler admin module and pick Run Bulk Configuration as the job type.
| Configuration | |
|---|---|
| Selects which bulk configuration the scheduler should run. | |
| Bulk Configuration | The bulk configuration to execute. The drop-down lists every configuration defined in the Bulk Processor admin module. Create, edit or remove configurations there — this job picks up whatever is currently defined under the selected name. |
The job does nothing if the selected configuration no longer exists, or if any of the processing steps the configuration references is provided by a bulk-processor plugin that is not installed on the server. In both cases an error is written to the scheduler log and the run ends without modifying any items.
What the job does when it runs
Every time the scheduler triggers the job it:
- Resolves the configured bulk configuration and every step it contains. A configuration that no longer exists, or a step whose module is not installed, ends the run with an error before a single item is touched.
- Searches the configuration's own table with its own work query and item source, exactly as the Bulk Processor would.
- Runs the steps over the found items in parallel, so the steps must not depend on the order items are processed in.
- Applies the steps to each item in the configured order. A step that fails skips the remaining steps for that item only and the run continues with the next item.