Skip to main content
A run is a single evaluation. When you launch a run, Coval triggers one or more simulations and evaluates the results against your metrics. A run can contain multiple conversations — for example, one per test case in your test set. Runs are launched from the Launch Simulations page — see Simulations. This page covers a few things around a run: organizing it with tags, the resource versions it executed against, and running it automatically on a schedule.

​
Tagging runs

You can add up to 20 tags to a run at launch time. Tags are useful for organizing and filtering runs — for example, by environment, release version, or test type. From the UI: A “Tags” card appears in the launch panel. Type a tag name and click + (or press Enter) to add it. Click the × on any tag chip to remove it. Via the API: Pass tags in the metadata.tags field of the launch request: 
{
  "agent_id": "...",
  "persona_id": "...",
  "test_set_id": "...",
  "metadata": {
    "tags": ["regression", "v2.1", "nightly"]
  }
}
Constraints: max 20 tags per run, each tag max 200 characters. After launch, you can filter simulations by tag using the tag= filter expression (e.g., tag="regression").

​
Resource versions and staleness

Coval keeps a version history for the resources a run uses. When you launch a run, it records the version of each resource it executed against, so its results stay interpretable even after you edit those resources later. In the run view, Coval flags when a run executed against an older version than the resource’s current one — a signal that the run may no longer reflect your latest configuration. When you see this, the run’s results were produced by a prior version; re-run against the current configuration to compare on equal footing. This staleness indicator is live for agents, personas, and metrics. Test sets are versioned too, but the run view does not yet flag a stale test-set version — that surfacing is coming.

​
Scheduled runs

Any evaluation can run on a recurring cadence to catch regressions and monitor agent quality over time. A scheduled run is backed by a template — each time the schedule fires, Coval launches a new run with that template’s exact configuration (agent, personas, test set, metrics, and mutations).

​
Creating a schedule

On the Launch page, set up your run (agent, personas, test set, metrics), then choose Launch ▾ → Schedule. In the dialog:
  • Schedule Name — optional; defaults to the template name.
  • Template Name — required. The schedule is saved as a template you can reuse and edit later.
  • Pick a schedule type:
Runs fire at a fixed cadence from when the schedule is created. Pick a preset — 15 or 30 minutes, hourly, every 6 or 12 hours, daily, weekly, or monthly — or set a custom interval anywhere from 15 minutes to 30 days.
Click Schedule. The schedule activates immediately.

​
Managing schedules

The Scheduled Runs page lists every schedule with its status (Active or Disabled), name, agent, cadence, backing template, and creation date. Search by name or ID, or filter by status.
  • Enable / Disable — pause a schedule without deleting it. Works on a single schedule or in bulk.
  • Edit Schedule — change the name or timing. This does not change what gets evaluated; edit the template for that.
  • Delete — only available once a schedule is disabled. This is permanent.
Click any schedule to open its run history — every run it has launched, with per-metric results, so you can spot regressions across consecutive runs.
To change what a schedule evaluates (agent, metrics, test cases), edit its template — the schedule always points to it.