> ## 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. # Let merges take turns with a merge queue > Set an on-merge Bolt schedule to Wait in line so merges run it one at a time, in merge order, and manage the queue from the schedule page. *October 8, 2026* The Bolt schedule Trigger type section with On merge selected and, under When merges overlap, Wait in line selected instead of Run in parallel When merge jobs take a while, two merges close together can deploy at the same time, and the second one assumes the first is already in production. An on-merge schedule can now make merges take turns. * **Wait in line.** On the **On merge** tab, under **When merges overlap**, choose **Wait in line**. Merges run the schedule one at a time, in merge order, and every merge still runs. **Run in parallel** stays the default. In YAML, set `concurrency: queue`. * **See and steer the queue.** A **Merge queue** card on the schedule's page shows the merge that's running and the merges waiting, with their pull requests. **Remove** takes a merge out of the queue, and **Run now** starts one out of turn. Both actions are recorded in the audit log. See [Merge queue](/products/bolt/ci-cd/chains#merge-queue). 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) - [Schedule Details](/products/bolt/managing-schedules/schedule-details.md) - [Run Turbo CI and merge schedules in order](/changelog/2026-10-08/ci-cd-chains.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.