Mergify incident

Duplicate queue status report comments on pull requests

Minor Resolved View vendor source →

Mergify experienced a minor incident on March 5, 2026 affecting Engine, lasting 2h 41m. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2026, 11:36 AM UTC
Resolved
Mar 05, 2026, 02:17 PM UTC
Duration
2h 41m
Detected by Pingoru
Mar 05, 2026, 11:36 AM UTC

Affected components

Engine

Update timeline

  1. identified Mar 05, 2026, 11:36 AM UTC

    We identified an issue where the merge queue was posting duplicate status report comments on pull requests. Instead of updating a single status comment per queue session, the system created a new comment on each queue cycle, resulting in a spam of comments on affected PRs. A fix is being deployed. Once applied, duplicate comments will stop. Existing duplicate comments are cosmetic and do not affect merge queue behavior or merging.

  2. monitoring Mar 05, 2026, 12:42 PM UTC

    Comment duplication has been mitigating, we're still investigating the issue.

  3. resolved Mar 05, 2026, 02:17 PM UTC

    The fix has been deployed and the duplicate queue status comments issue is now resolved. Pull requests will no longer receive multiple status report comments per queue cycle.