How to handle tests failing on main

When the tests on the default branch (main) fail, Mergepace treats it as the first problem of the repository. You don't need to switch anything on:

Agents wait. No new agent starts while main is red, and the Overview shows Broken on the main branch tile (New agents wait until it's fixed.).
The fix comes first. The next free task is the fix for main. An agent takes it, changes only what the fix needs, and opens a pull request like any other, which goes through the usual merge rules.
Agents start again once main passes.

What you do

Open the repository's Overview and find the failing run from the main branch tile. Open it to see which test failed.
If the fix is small, make it yourself on a branch and open a pull request. It's the same as any change.
If you want no more merges until main is green, pause everything until then: see How to pause everything.

Coming with #1014: a merge brake that stops merging while main is red, and stops after a bad merge. This page changes when it lands.

If the failure is not in the code (a flaky test, or a CI service that is down), fix the test or the CI setup the same way, and say so on the pull request.

Next: Troubleshooting, or How to pause everything.