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

# Run Turbo CI and merge schedules in order

> Chain Bolt Turbo CI and on-merge schedules so they run in order on each pull request and merge, stop at the first failure, and report each step to GitHub.

*October 8, 2026*

<Frame>
  <img src="https://mintcdn.com/paradime-docs/XrvgZchMz165UuEn/images/bolt-turbo-ci-chain-github-checks.jpg?fit=max&auto=format&n=XrvgZchMz165UuEn&q=85&s=0360b135d2386018fe6c0064a282403f" alt="GitHub pull request checks with Paradime Turbo CI running CI-pre-commit and CI-dbt as separate Paradime Turbo CI checks, and Paradime Lineage Diff waiting for Turbo CI" width="1600" height="900" data-path="images/bolt-turbo-ci-chain-github-checks.jpg" />
</Frame>

Bolt can now run your Turbo CI and on-merge schedules in the order you choose. A **chain** starts each step only after the step before it finishes with the result you picked, so a failed build stops the steps after it instead of everything running at once.

* **Build it in the form or in YAML.** On the **Turbo CI** and **On merge** tabs, turn on **Run after another schedule** and pick the step before. In YAML, use `run_after`, a clearer alias for `schedule_trigger`.
* **One chain per pull request and per merge.** Pull request steps run on the latest commit, in the pull request's schemas, and a new push restarts the chain. Merge steps build the merge commit, even if more commits land while they run.
* **One check per step on GitHub.** With two or more Turbo CI schedules, each step gets its own `Paradime Turbo CI / <schedule name>` check, and `Paradime Turbo CI` holds the overall result. Select **Re-run** on a step's check to run that step and the steps after it again. After a merge, one **Paradime Merge Run Summary** comment covers the whole chain.
* **Retry Turbo CI and merge runs.** These runs couldn't be retried before. On the run page, **Retry this step** runs the step and the steps after it again, and **Retry the whole chain** starts again from the first step. They can't be retried from the API, CLI, or SDK, because the steps after them wouldn't run.

Chains need the Paradime GitHub app. To make merges take turns, see the new [merge queue](/changelog/2026-10-08/merge-queue). See [Chains](/products/bolt/ci-cd/chains). Shipped in Paradime v6.18.0.


## Related topics

- [Changelog](/changelog/overview.md)
- [Run Bolt schedules in order on pull requests and merges](/products/bolt/ci-cd/chains.md)
- [Set up a GitHub merge queue with Paradime Turbo CI](/guides/working-with-git/github-merge-queue.md)
- [Bolt CI/CD for dbt™ pull requests and deploys](/products/bolt/ci-cd/index.md)
- [Turbo CI on GitLab merge requests](/products/bolt/ci-cd/turbo-ci/gitlab.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.