Schedule

A batch (scheduled execution of a set of transformations) is a datasqill entity that can be executed on a time-triggered basis. The batch also defines the scope of the running transformations through the batch elements.

The edit mode for batches works similarly to worksheets. In edit mode, batch elements can be added. A batch element can be a single transformation, a worksheet, and/or a directory. In our concrete case, a directory is used that contains both worksheets. It is generally recommended to use as coarse-grained batch elements as possible (i.e. better a directory than a worksheet, better a worksheet than a transformation), because then the automatic datasqill execution control works most effectively.

A batch can be scheduled flexibly with different frequencies: DAILY, MONTHLY, WEEKLY, INTERVAL IN MINUTES. This also enables intraday executions. See more under Concepts > Scheduled Runs

The "Next Run Date" attribute always shows the next execution date and is useful for verifying the scheduling settings.

There is an option to define dependencies between batches, including between instances of a batch (which is useful e.g. for recurring batches and can ensure that no new instance is started as long as the previous one is still running). The screenshot shows a configuration example for a batch that runs every 60 minutes but skips an execution if the previous instance is still running.