MacOS jobs without a resource class set will not run

This incident has been resolved.

All jobs should now be running normally. The backlog of jobs has cleared and jobs should be running in typical time. We will continue monitoring to ensure consistent service. Thank you for your patience.

We are continuing to see recovery, but some customers may still experience delays in jobs running on M4 executors. We appreciate your patience whilst we work through the backlog of jobs.

We have mitigated the issue and MacOS jobs which do not have a resource class specified should run normally. Customers can rerun jobs which failed an they should now run normally without any modification to their config. Thank you for your patience whillst we resolved this.

Customers using M4 machine jobs may experience minor delays in jobs starting during this period as there are a large number of re-runs occurring.

We have identified an issue in our system which mean that MacOS jobs which don't specify a resource class will fail to run with an "Invalid resource class" error. We are working to correct this, but customers can workaround this by specifying a resource class in their config.yml.