CircleCI "resource class is not available" on this plan in CI

By Daniel Zoghalchali·Latchkey

A job requested a resource_class that CircleCL will not schedule: it is not on the org plan, not valid for that executor type, or has been retired. The job is rejected at spin-up.

What this error means

The job fails to start with "resource_class [X] is not available" or "is not a valid resource class for the [docker|machine] executor".

resource_class 'xlarge' is not available for your plan or executor type.

Common causes

The class is not enabled for the plan

Larger classes (and some executor-specific ones) require a plan tier that the org does not have.

The class is wrong for the executor type

Docker, machine, and arm executors have different valid class names; mixing them fails validation.

How to fix it

Use a class valid for the executor and plan

1. Check which classes your plan enables.
2. Pick a valid class name for that executor type.
3. Re-run with the supported class.

jobs:
  build:
    docker: [{image: cimg/node:20.11}]
    resource_class: medium

Upgrade the plan for larger classes

If you genuinely need a bigger class, enable it on the org plan rather than forcing an unavailable name.

How to prevent it

• Use resource class names valid for each executor type.
• Confirm plan availability before requesting large classes.
• Avoid deprecated class names in config.

Frequently asked questions

Related guides

References

• GitHub Actions documentation