validate

The validate command has two independent modes. One requires a flag: --scenarios or --runs.

`validate --scenarios`

Inspect and lint scenario definitions: checks JSON schema, field consistency, host/agent references, and validation rule structure, and verifies that referenced agent, host, and specialty IDs exist in the database (so it needs a database connection). Does not execute the scenario. Useful after editing scenario.json files to catch errors before a full run.

# Inspect all scenarios
2501 runner validate --scenarios

# Inspect scenarios matching a tag or explicit key
2501 runner validate --scenarios nginx
2501 runner validate --scenarios nginx/001-broken-config

Option	Description
`[filter]`	Optional. Scenario filter: tags or explicit key. Omit to inspect all.
`-p, --scenarios-path <path>`	Path to scenarios directory (auto-detected if omitted).

`validate --runs`

Re-runs the validation rules for a scenario against an existing job, task, or benchmark, without re-executing the scenario. Use this when iterating on validation rules and you don’t want to wait for another full agent run. Scenario run results are also visible in the Benchmark page in Command Center.

runner validate --runs --job-id <job-id>
runner validate --runs --task-id <task-id>
runner validate --runs --benchmark-id <benchmark-id>

Option	Description
`--job-id <id>`	Job to validate against.
`--task-id <id>`	Task to validate against.
`--benchmark-id <id>`	Validate all runs for a benchmark.
`-s, --filter <list>`	Override the scenario key (auto-detected from the existing run if omitted).
`--from <type>`	Validation source: `gateway` \| `job` \| `task` (default: `job`).
`-g, --gateway <type>`	Gateway type (`servicenow`). Required when `--from gateway`.
`--env-file <path>`	Path to env file (auto-detected if omitted).
`-v, --verbose`	Show detailed output.

Get Started

Authoring

Running

VM Sandbox

`validate --scenarios`

`validate --runs`

​validate --scenarios

​validate --runs

`validate --scenarios`

`validate --runs`