---
title: "The autoqueue queue rule option has been removed"
date: 2026-10-21
tags:
  - "Merge Queue"
  - "Deprecations"
description: "The queue rule option `autoqueue` no longer exists. Configure automatic queuing with `auto_merge_conditions` in `merge_protections_settings` instead."
---

The `autoqueue` option on a queue rule, and in `defaults.queue_rule`, has been removed. It was deprecated in favor of `merge_protections_settings.auto_merge_conditions`, which decides the same thing (whether Mergify queues a pull request on its own) for the whole repository rather than per queue rule.

A configuration that still sets `autoqueue` is no longer valid, so Mergify stops running on that repository until the key is gone. Replace it with `auto_merge_conditions: true` under `merge_protections_settings` to keep queuing every pull request automatically, or with a list of conditions to choose which ones. Each queue rule's own `queue_conditions` still decides which queue a pull request enters.

Mergify keeps opening a pull request that makes this change for you. `auto_merge_conditions` requires the Merge Protections product: if it is not enabled on the repository, enable it in the Mergify dashboard and Mergify will migrate `autoqueue` for you. Removing `autoqueue` by hand also gets Mergify running again, but pull requests then stop being queued automatically.

See [Auto-merge](https://docs.mergify.com/merge-protections/auto-merge/) for the full syntax.