2. Command Settings

After configuring Schedule Settings of a Bolt Schedule, you’ll specify the commands you want the schedule to execute. Command Settings allow you to define which commands run when the schedule is triggered, supporting a variety of workflows.

Overview

With Command Settings, you can:

• Select commands (dbt™, Elementary Data, and others) to run in Paradime

• Set the order of command execution

• Customize options for each command

• Create custom command combinations to suit your workflows

Commands execution logic

Paradime follows a specific command execution logic to handle errors and determine whether subsequent tasks should be executed. Here's how it works:

1. Command Completion with Error: When a command in a Paradime schedules completes with an error, the subsequent tasks in the job will be skipped by default.

2. Exceptions to Skipping Subsequent Tasks: Despite the default behavior of skipping subsequent tasks on error, there are a few exceptions where the subsequent tasks will still be executed:

   1. Source Freshness and Source Status: If the command that encountered an error is a dbt source freshness command and the following command is using the source_status:fresher dbt™ selector method, the subsequent command will still be executed (Check our Bolt Template).

   2. Elementary CLI Command: If the next command in the schedule is an Elementary CLI command, it will be executed regardless of the error in the previous command to enable sending alerts and generating reports on tests failures.

   3. Montecarlo Command: If the next command is a Montecarlo command, it will be executed even if the previous command encountered an error to upload dbt™ resources.

Explore Paradime Supported Commands in Bolt

dbt™ Commands

Python Scripts

Elementary Commands

Lightdash Commands

Tableau Workbook Refresh

Power BI Dataset Refresh

Paradime Bolt Schedule Toggle Commands

Monte Carlo Commands