Bolt Pipelines - Paradime

Paradime’s Bolt is a comprehensive orchestration solution for deploying dbt™ in production. Instead of manually running commands, take advantage of Paradime’s built-in scheduling to configure and automate your entire scheduling workflow.

PrerequisitesScheduler Environment is connected to your data warehouse provider.

Coming from dbt Cloud™️? Import all your dbt™️ jobs with one click. See our doc here.

Key Benefits

Maintain fresh production data on a consistent schedule
Execute CI/CD and production pipelines efficiently
Swiftly identify and resolve deployment issues
Utilize native integrations and custom webhooks for enhanced deployment

Documentation Sections

Schedule Anatomy

🧩 Understand the building blocks of a schedule: settings, commands, triggers, notifications, environment variables, and self-healing.

Deploy Schedules

📅 Build and ship schedules through the UI or as code with YAML, and start from pre-built job templates.

Managing Schedules

🔄 Discover how to monitor schedule performance, analyze run logs, and troubleshoot issues in your active schedules.

CI/CD

🚀 Find setup instructions and best practices for implementing continuous integration and deployment with various version control platforms.

Bolt API

🔌 Trigger, monitor, and retry Bolt runs programmatically, including from external orchestrators like Airflow and Dagster, via the API, SDK, CLI, or webhooks.

New to Bolt? Start with Schedule Anatomy to learn the building blocks, then Deploy Schedules to set up your first automated workflow.

Bolt Terminology

Understanding these key terms is crucial when configuring your schedules:

Term	Description	Example	Required
Schedule Type	Execution type for your scheduled dbt™ run	`Standard`, `Deferred`, or `Turbo CI`	Yes
Name	Identifier for your dbt™ schedule	`hourly_schedule`	Yes
Description	The purpose of your bolt Schedule	`schedule dbt run on an hourly basis`	Yes
Owner Email	Schedule owner’s email	`me@email.com`	Yes
Git Branch	Branch used for schedule execution	`main`	Yes
Commands	dbt™ commands to execute (can be multiple)	`dbt run` `dbt test`	Yes
Trigger Type	How the schedule is initiated	`Scheduled run`, `On Run Completion`, `On Merge`	Yes
Cron Schedule	Frequency of schedule runs (UTC-based) for Schedules Runs	@hourly	No
SLA Threshold	Trigger an alert when the schedule has passed a time threshold (minutes)	`30`	No
Notification Destination	The destination of a notification	`Email`, `Slack`, and/ or `MS Teams`	No
Notification Type	Notifications received after a scheduled run	`Success`, `Failure`, `SLA`	No

​Key Benefits

​Documentation Sections

Schedule Anatomy

Deploy Schedules

Managing Schedules

CI/CD

Bolt API

​Bolt Terminology

Key Benefits

Documentation Sections

Bolt Terminology