---
title: "Enable, repoint, or disable a suite's schedule"
method: PATCH
path: "/projects/{projectId}/eval-suites/{suiteId}/schedule"
tags: ["Eval runs"]
---

# Enable, repoint, or disable a suite's schedule

`PATCH /projects/{projectId}/eval-suites/{suiteId}/schedule`

A schedule fires exactly ONE run per interval, so an environment-based suite must pin exactly one of its attached environments. Omitting `environmentId` on a single-environment suite means that environment; omitting it on a multi-environment suite is a VALIDATION_ERROR. Disabling preserves the existing pin. Responds with the full updated suite.

## Path parameters

- `projectId` string, required
- `suiteId` string, required

## Request body

- EvalSuiteScheduleRequest — Enable, repoint, or disable a suite's recurring runs. Disabling PRESERVES the existing environment pin — send `enabled: true` with a new `environmentId` to repoint it.
  - `enabled` boolean, required
  - `intervalMinutes` integer
  - `environmentId` string — Which attached environment scheduled runs use. Only meaningful when enabling. Omitted on a single-environment suite means that environment; omitted on a multi-environment suite is a VALIDATION_ERROR.

## Response `200`

The updated suite.

- EvalSuiteDetail — One eval suite's full configuration. Distinct from the `EvalSuite` summary returned by the list route, which carries run rollups instead of settings.
  - `id` string, required
  - `name` string, nullable
  - `description` string, nullable
  - `projectId` string, nullable
  - `environment` object, required — LEGACY server bag, kept as rollback data, plus the suite's sandbox-image pin. Unrelated to `environmentIds`.
    - `servers` string[]
    - `computerEnvironment` EvalSuiteComputerEnvironment — The sandbox image a suite's eval runs boot from.
      - `id` string, required
      - `name` string, nullable, required — The image's name, resolved for you so a caller can echo back what it set. `null` when the pinned image could not be resolved (deleted, or not visible to this caller).
  - `executionConfig` object, nullable
    - `model` string
    - `systemPrompt` string
    - `temperature` number
  - `hosts` object[], required
    - `id` string, required
    - `name` string, required
    - `servers` string[]
  - `environmentIds` string[] — Attached project environments, in attach order.
  - `settings` object, required
    - `minimumAccuracy` number, nullable — Minimum pass rate for the suite to count as passing.
    - `minimumIterations` number, nullable — Suite-level floor on per-case iterations, 1–10: every case runs at least this many times (`max(case.iterations, minimumIterations)`). `null` means no floor — the suite's real state, not a stand-in for 1. PATCH `null` to remove it.
    - `matchOptions` object, nullable
    - `checks` object[]
    - `judge` object — Goal-completion judge (LLM as Judge), FULLY RESOLVED: every field is the platform default where the suite set none, so this is what a run on this suite would actually grade with.
      - `enabled` boolean — Judge is available on the suite. On its own this grades nothing.
      - `model` string, nullable — Resolved judge model. `null` only from deployments that predate resolution.
      - `autoRun` boolean — The flag that makes grading HAPPEN: grade every run as it completes. Spends per run.
      - `threshold` number — Advisory pass threshold, 0–1 (`passed = score >= threshold`).
  - `schedule` EvalSuiteSchedule, required — Recurring-run schedule. A schedule fires exactly ONE run, so an environment-based suite pins the environment it runs against.
    - `enabled` boolean, required
    - `intervalMinutes` integer, nullable — Minutes between runs. 5 minutes to 7 days.
    - `environmentId` string, nullable — The single attached environment scheduled runs use. Null on a legacy (non-environment) suite.
  - `createdAt` number, nullable — Epoch milliseconds.
  - `updatedAt` number, nullable

## Other responses

- `400` — Malformed body or parameters.
- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `409` — The resource is not in a state that accepts this write — a stale `expectedRevision`, a duplicate name, or an environment that cannot currently be launched. The request was well-formed; re-read the resource and retry.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.
- `502` — Could not connect to the target MCP server.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/8bf151c2dd8b/schema)