> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/bolt/creating-schedules/schedules-as-code.md).

# 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.

{% hint style="info" %}
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.
{% endhint %}

{% hint style="warning" %}
**Prerequisites**

To run YAML-based schedules, connect your data warehouse to the [Scheduler Environment](/app-help/products/settings/connections/scheduler-environment.md).
{% endhint %}

**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?

1. **Version Control**
   * Schedule configurations are tracked alongside your dbt models
   * Review schedule modifications through Pull Requests
   * Enforce team review processes for schedule changes
2. **Infrastructure as Code**
   * Schedules are treated as code, not just UI configurations
   * Easy replication across environments
   * Enables automated deployment pipelines
3. **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**.

{% hint style="info" %}
💡 **Note**: To update your schedules, make sure to merge your changes to the deployment branch first.
{% endhint %}

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.paradime.io/app-help/products/bolt/creating-schedules/schedules-as-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.