Tagging runs
Tags label runs so you can organize and filter them — for example, by environment, release version, or test type. A run can carry up to 20 tags, each up to 200 characters. At launch: Add tags in the Tags section of the Simulate page before you click Launch. After launch: Use the tag control in the results header of a run, a simulation result, or an uploaded conversation’s results. From there you can search existing tags, create new ones, and rename or recolour a tag. Tags are stored on the run, so where you add one matters:- Tagging a run tags every simulation in it.
- Tagging a simulation result tags its parent run — and therefore every simulation in that run.
- Tagging an uploaded conversation tags only that conversation, because each uploaded conversation has a run of its own.
metadata.tags field of the launch request, or change them later with Update run:
tag= filter expression (e.g., tag="regression").
Passing run metadata to an inbound SIP agent
When an inbound SIP agent needs launch-specific connection context, add the values tometadata.customer and reference them from the agent’s custom SIP headers with {{run_metadata.<key>}}.
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 Simulate 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:
- Interval-based
- Time of Day
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.
Managing schedules
Open Scheduled (from the sidebar, or the Scheduled button on the Simulated Conversations page). It 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.
To change what a schedule evaluates (agent, metrics, test cases), edit its template — the schedule always points to it.