{
  "doc": {
    "id": "cloud/features/smart-orchestration/spec-prioritization",
    "title": "Spec Prioritization",
    "description": "Run failed specs first to save time and reduce CI costs with Cypress Cloud's Spec Prioritization feature.",
    "section": "cloud",
    "source_path": "/llm/markdown/cloud/features/smart-orchestration/spec-prioritization.md",
    "version": "a8fd16711bdda4c7b5645b9717e588ae99ec2470",
    "updated_at": "2026-05-18T17:21:32.047Z",
    "headings": [
      {
        "id": "cloud/features/smart-orchestration/spec-prioritization#spec-prioritization",
        "text": "Spec Prioritization",
        "level": 1
      },
      {
        "id": "cloud/features/smart-orchestration/spec-prioritization#what-youll-learn",
        "text": "What you'll learn",
        "level": 5
      },
      {
        "id": "cloud/features/smart-orchestration/spec-prioritization#activate-spec-prioritization-in-cypress-cloud",
        "text": "Activate Spec Prioritization in Cypress Cloud",
        "level": 3
      }
    ]
  },
  "chunks": [
    {
      "id": "cloud/features/smart-orchestration/spec-prioritization#what-youll-learn",
      "doc_id": "cloud/features/smart-orchestration/spec-prioritization",
      "heading": "What you'll learn",
      "heading_level": 5,
      "content_markdown": "##### What you'll learn\n\n*   How to enable Spec Prioritization in Cypress Cloud\n*   How to save time by running failed specs first\n*   How to reduce CI costs by using Spec Prioritization with Auto Cancellation\n\nIt is often helpful to be **aware of test failures earlier within a CI test run so that debugging and iterations can resume and progress much faster**. Being able to catch issues sooner within the CI process can save valuable time in troubleshooting failures and deploying fixes.\n\nFor example, consider you have a test suite consisting of several spec files that take **30 minutes** to execute, but failures start to occur within one spec at the **20 minute** marker. A subsequent code change aimed at resolving the issue will have to be validated after running the CI build and waiting **20 minutes**. This process and waiting continues until the issue is fixed.\n\nBy running failed specs first, the issues can be surfaced earlier and reduce that 20 minute wait to potentially a few minutes. **Considering that a test suite has multiple spec files, this orchestration strategy will always save time.**\n",
      "section": "cloud",
      "anchors": [
        "what-youll-learn"
      ],
      "path": "/llm/json/chunked/cloud/features/smart-orchestration/spec-prioritization.json",
      "token_estimate": 248
    },
    {
      "id": "cloud/features/smart-orchestration/spec-prioritization#activate-spec-prioritization-in-cypress-cloud",
      "doc_id": "cloud/features/smart-orchestration/spec-prioritization",
      "heading": "Activate Spec Prioritization in Cypress Cloud",
      "heading_level": 3,
      "content_markdown": "### Activate Spec Prioritization in Cypress Cloud\n\n**Spec Prioritization** is a _Smart Orchestration_ feature available to users with a [Business or Enterprise tier Cypress Cloud plan](https://cypress.io/pricing). Wondering if upgrading your Team tier subscription is worth it? Check out the [recommendations](/llm/markdown/cloud/features/recorded-runs.md#Recommendations) on the run overview page to see how much time we predict these features would save you.\n\nSpec Prioritization is a _Smart Orchestration_ feature that is managed within a project's settings.\n\n**To enable or disable this feature at the Project level (must be an admin user):**\n\n1.  Select the desired project within Projects view to visit Cypress Cloud.\n2.  Click \"Project Settings\" with the right-hand sidebar.\n3.  Scroll to the Smart Orchestration section within Project Settings page.\n4.  Toggle \"Spec Prioritization\".\n\n**CI Tip: Reduce Costs**\n\nNote that Spec Prioritization **alone** will not save time as it purely alters the order in which specs are run. However, when used in tandem with [Auto Cancellation](/llm/markdown/cloud/features/smart-orchestration/run-cancellation.md) it can result in shorter test runs due to cancellation being triggered earlier, leading to significantly reduced CI costs.\n",
      "section": "cloud",
      "anchors": [
        "activate-spec-prioritization-in-cypress-cloud"
      ],
      "path": "/llm/json/chunked/cloud/features/smart-orchestration/spec-prioritization.json",
      "token_estimate": 229
    }
  ]
}