Skip to main content
A run is a single execution of a monitor. Each time the scheduler triggers a monitor (or you trigger one manually), a new run is created.

​
Viewing runs

# Recent runs across all monitors
griffin runs

# Runs for a specific environment
griffin runs production

# Filter by monitor
griffin runs --monitor health-check

# Show more results
griffin runs --limit 50

​
Run details

Each run tracks:
FieldDescription
Statuspending, running, completed, or failed
Triggered byschedule (automatic), manual (via CLI), or api
Started atWhen execution began
Completed atWhen execution finished
DurationTotal execution time in milliseconds
SuccessWhether all assertions passed
ErrorsAny error messages from failed nodes

​
Run statuses

  • Pending — The job is queued and waiting for an executor
  • Running — An executor is currently processing the monitor
  • Completed — Execution finished (check success for pass/fail)
  • Failed — Execution encountered an error (timeout, network failure, etc.)

​
Triggering runs manually

# Trigger a run
griffin run --monitor my-test

# Trigger and wait for results
griffin run --monitor my-test --wait

# Trigger in a specific environment
griffin run production --monitor my-test
Manual runs execute immediately regardless of the monitor’s frequency schedule.