---
title: Pausing the Merge Queue
description: Understand the pause feature and how to use it during CI incidents.
---

Pausing Mergify's Merge Queue suspends its automation, typically during a CI
incident. This page explains what pausing does, its impacts, and when to use
it.

## What Does Pausing Do?

When you pause the merge queue:

1. **Suspended**: The merge queue will be suspended.

2. **Addition to the Queue Continues**: Even with a paused merge queue, new
   pull requests can still join the queue. This ensures pull requests remain
   organized and ready for when operations resume.

3. **Stops Scheduling and Actions**: After pausing the merge queue, Mergify
   will not schedule new checks or merge pull requests. Pull requests can enter
   the queue but won't be acted upon.

4. **Cancel Running Checks**: When you pause the queue, Mergify attempts to
   cancel any running checks for pull requests that are in the queue and will
   wait for the queue to be resumed.

   :::note
   This cancellation does not apply to checks that are running in
   place (i.e., checks that run directly on the pull request rather than on a
   temporary merge commit). Those running checks are not cancelable: if they
   fail while the queue is paused, the associated pull request will be removed
   from the merge queue as the queue conditions will not match anymore.
   :::

## How to Pause the Merge Queue

### From the Dashboard

Navigate to your [Mergify dashboard](https://dashboard.mergify.com). There
you'll find an option to pause the merge queue. Clicking on this will suspend
the queue.

<Image alt="Pause button is in the top right corner in Mergify's dashboard" src={screenshotButtonPause} />

### Using the CLI

Pause the queue from the terminal with a reason (required):

```bash
mergify queue pause --reason "deploying hotfix"
```

Resume when ready:

```bash
mergify queue unpause
```

See the [`queue` CLI reference](/cli/queue) for all pause options and the rest
of the queue commands.

### Using the API

You can also pause the merge queue programmatically using the [Mergify
API](/api/usage).

## Typical Use Cases

### CI Incidents

During a major incident with the CI system, if checks are likely to fail and
eject pull requests from the queue, pause the merge queue until the incident
is resolved.

### Non-CI Incidents

If an incident is unrelated to the CI, like a production issue, but you wish to
halt merging while allowing checks to run, then the [scheduled freeze
feature](/merge-protections/freeze) is a more suitable choice.

## Benefits of Using the Pause Feature

1. **Maintain Queue Integrity**: During CI failures or other disruptions,
   pausing ensures pull requests stay in the queue, preserving their order.

2. **Flexibility**: It provides an immediate response tool during unexpected
   complications, giving you control over the merge process.

3. **Reduce Noise**: Constantly failing checks during a CI incident can create
   unnecessary notifications. Pausing the queue mitigates this.