Status¶
This command provides a single, high-level operational summary without needing to dig into the database manually.
If this command fails on an older schema-version-5 database, migrate the schema first:
uv run loreley db migrate
Usage¶
uv run loreley status
It displays:
- Experiment and root commit information.
- The number of unfinished and pending-ingestion jobs.
- Job lease health for
RUNNINGjobs, including stale and recovery-exhausted counts. - The current lease TTL, heartbeat interval, and max recovery budget.
- Selected-island MAP-Elites statistics (occupied cells, coverage, retained elites, objective count).
- The best retained commit by the configured primary objective, labelled as such.
- Current root baseline status when a matching campaign baseline is known, including status, metric, value, baseline key, and failure kind.
Options¶
--island-id: Inspect a specific island. If omitted, uses the first ID inMAPELITES_ISLANDS.--json: Print the status payload as JSON, useful for machine-readable integrations.
Lease health¶
The status payload includes a job_leases section. Use it to answer these questions quickly:
- Are there any
RUNNINGjobs right now? - Did any
RUNNINGjobs stop heartbeating and become stale? - Are there any malformed
RUNNINGrows with missing lease fields? - Have any jobs already exhausted the automatic stale-recovery budget?
For step-by-step triage and manual retry instructions, see Job lease recovery.
Baseline status¶
When a campaign baseline row matches the current experiment root, campaign
program, evaluator identity, primary metric, runtime profile, and settings
fingerprint, status adds a baseline section.
In JSON output this appears as baseline with fields such as:
campaign_baseline_idbaseline_key_hashroot_baseline_metricroot_baseline_valueroot_baseline_statusbaseline_campaign_program_hashfailure_kindfailure_summary
If no active campaign program or matching baseline is known, baseline is
null.