Builds stuck in "Queued" state on Mac mini M2 despite available minutes

[ffu52848]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

1.Trigger a manual build for the "Default Workflow" on the main branch.

2.The build remains in the "Queued" state for more than an hour.

3.Tried canceling and restarting the build (Index 240 and 241) multiple times, but it stays stuck at "Preparing build machine".

4Verified that the account has ~180 build minutes remaining.

Expected results

The build should start on the allocated Mac mini M2 instance within a few minutes.

Actual results

The build is permanently stuck in the "Queued" state. The status page shows "All systems operational," but the virtual machine is not being assigned to my project.

Build id (optional)

69f16ed3ad0e0c469f7f7123,69f16fbbd3570da4fd2c5997,69f17352932527b21a7f5bb4

[Gyeony95]

I'm in the same situation. I'm using M4 and trying to build a Flutter app, but it's not moving out of the queue.

[ffu52848]

Thanks for sharing. Since this is happening across both M2 and M4 instances, it’s almost certainly a backend provisioning issue or a silent failure on Codemagic's side, regardless of what their status page says. Hopefully, catches this traffic jam soon!

[mstainer14]

Facing the same issue, I am on the pay as you go plan, and seems to affect iOS only. My Android build on a Linux machine completed as normal.

[ffu52848]

the status page claims 'all systems operational.' It seems the macOS build farm is having a silent failure. Thanks for confirming that even Pay-as-you-go isn't getting through

[icarusdust]

@ffu52848, @Gyeony95, @mstainer14. The issue was already identified and resolved, with the status page reflecting it. Sorry for the inconvenience.