> ## Documentation Index > Fetch the complete documentation index at: https://docs.paradime.io/llms.txt > Use this file to discover all available pages before exploring further. # Commands > Add commands to a Paradime Bolt schedule: run dbt™, trigger data syncs and orchestration, refresh BI dashboards, run data quality checks, and more. After configuring the [Triggers](/products/bolt/creating-schedules/trigger-types) and [Schedule settings](/products/bolt/creating-schedules/schedule-settings) of a Bolt schedule, you add the **commands** the schedule runs. Commands run in order, so you can chain a full pipeline: sync sources, run dbt™ transformations, run data quality checks, then refresh dashboards. To add a command, open a schedule, click **Add command**, and pick a command type from the categories below. Each command type has its own modal: some expose structured fields, others accept any command the underlying [Paradime CLI](/developers/paradime-cli/index) supports. ## Commands execution logic Paradime follows a specific execution logic to handle errors and decide whether later commands run: 1. **Command completes with an error**: by default, the remaining commands in the schedule are skipped. Use [Continue on error](#continue-on-error) to change this. 2. **Exceptions that still run after an error**: * **Source freshness and source status**: if a [`dbt source freshness`](/guides/dbt-fundamentals/running-dbt/mastering-the-dbt-cli/commands#source-freshness) command errors and the next command uses the [`source_status:fresher`](/guides/dbt-fundamentals/running-dbt/mastering-the-dbt-cli/methods#source_status-method) selector, the next command still runs. * **Elementary**: an [Elementary](/products/bolt/creating-schedules/command-settings/elementary-commands) command runs regardless of a previous error, so you can send alerts and generate reports on test failures. * **Monte Carlo**: a [Monte Carlo](/products/bolt/creating-schedules/command-settings/monte-carlo-commands) command runs regardless of a previous error, so dbt™ artifacts are always uploaded. ### Continue on error You can override the default skip behavior at two levels in the Commands section of the schedule form: * **Schedule level**: turn on the **Continue on error** toggle to keep running the remaining commands when one fails. The run is still reported as failed. * **Per command**: each command row has a select with three options: **Default** (inherit the schedule-level setting), **Continue** (keep going even if this command fails), or **Stop** (skip the remaining commands if this command fails). Per-command settings override the schedule-level toggle, so you can, for example, continue past a failing `dbt test` while still stopping the pipeline if `dbt run` fails. Set `continue_on_error` at the schedule level or per command in `paradime_schedules.yml`. ## Commands library ### AI ### Transform & code ### Data quality ### BI & dashboards ### Data sync ### Orchestration ### Cloud compute ### Data catalog ### Core ## Related topics - [Commands](/guides/dbt-fundamentals/running-dbt/mastering-the-dbt-cli/commands.md) - [bolt.run.completed](/developers/webhooks/bolt-run-completed.md) - [Alert Templates](/products/bolt/creating-schedules/alert-templates.md) - [dbt™ Commands](/integrations/pre-commit/dbt-tm-checkpoint-hooks/dbt-tm-commands.md) - [Run dbt™ Command](/products/bolt/creating-schedules/command-settings/dbt-tm-commands.md)