Schedules as Code

What are Paradime YAML-Based Schedules?

Paradime YAML schedules are configuration-as-code definitions, allowing you to define, version, and manage your data pipeline schedules directly within your dbt project repository. The recommended layout is the .bolt/ folder — a directory at the root of your dbt project containing one or more YAML files, each declaring a set of schedules. This lets teams own their own files and avoid merge conflicts on a shared configuration.

The legacy single-file paradime_schedules.yml at the project root is still fully supported. The two layouts can coexist, so you can adopt .bolt/ gradually.

PrerequisitesTo run YAML-based schedules, connect your data warehouse to the Scheduler Environment.

File Location

your-dbt-project/
├── dbt_project.yml
├── .bolt/                       # recommended — modular layout
│   ├── transforms/
│   │   └── marketing.yaml
│   └── ci/
│       └── pull-requests.yaml
├── paradime_schedules.yml       # legacy — still supported
├── models/
└── ...

See Modular Schedules with the .bolt/ Folder for the folder layout’s discovery rules and examples.

Why Use YAML-Based Schedules?

Version Control
- Schedule configurations are tracked alongside your dbt models
- Review schedule modifications through Pull Requests
- Enforce team review processes for schedule changes
Infrastructure as Code
- Schedules are treated as code, not just UI configurations
- Easy replication across environments
- Enables automated deployment pipelines
Team Collaboration
- Simplified schedule review process
- Standard formatting and validation
- Documentation lives with the code

How YAML-based schedules are deployed

Schedules are read from your repository’s default branch (usually main or master). If you’ve configured a custom schedule deployment branch, that branch is used instead.

Automatic Refresh: Paradime checks for changes every 10 minutes.
Manual Refresh: For immediate updates, navigate to the Bolt interface and click Parse Schedules.

💡 Note: To update your schedules, make sure to merge your changes to the deployment branch first.

You can also edit, create, and delete schedule files directly in the Paradime UI — see Editing YAML schedules from the Paradime UI.

​What are Paradime YAML-Based Schedules?

​Why Use YAML-Based Schedules?

​How YAML-based schedules are deployed

What are Paradime YAML-Based Schedules?

Why Use YAML-Based Schedules?

How YAML-based schedules are deployed