> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noisemaker.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Runs and measurement

> Choose a preset, follow the job lifecycle, and inspect a completed run.

<Frame caption="Measurement runs and their status.">
  <img src="https://mintcdn.com/auto-gtm/iXt5uMxsbIiTmJfR/images/console-runs.png?fit=max&auto=format&n=iXt5uMxsbIiTmJfR&q=85&s=5fb4e413873b3a6c0688b3ba83f59d3c" alt="Measurement runs and their status." width="2880" height="1800" data-path="images/console-runs.png" />
</Frame>

A run sends active prompts to the engines in a preset and stores the provider evidence used for GEO metrics and reports.

## Presets

| Preset                | Engines                                       | Repeats | Prompt cap | Budget ceiling |
| --------------------- | --------------------------------------------- | ------: | ---------: | -------------: |
| <code>smoke</code>    | Perplexity, Gemini                            |       1 |          2 |         \$0.50 |
| <code>lite</code>     | Perplexity, Gemini, Claude                    |       1 |         50 |         \$5.00 |
| <code>standard</code> | Seven configured engines with per-engine caps |       1 |        150 |        \$18.00 |
| <code>exa</code>      | Exa, Exa Search                               |       1 |        150 |         \$3.00 |

The CLI also defines a <code>deep</code> preset with three repeats and a \$110 ceiling. The web application currently accepts <code>smoke</code>, <code>lite</code>, <code>standard</code>, and <code>exa</code>.

The start screen estimates prompt count, calls, and cost from active prompts and observed provider pricing. The preset ceiling remains a hard upper bound, not a promised charge.

## Start a run

<Steps>
  <Step title="Select a preset">
    Confirm its engine mix and prompt coverage.
  </Step>

  <Step title="Review the reservation">
    The application reserves the estimated micro-USD amount across available credit lots.
  </Step>

  <Step title="Launch the job">
    The web worker starts an allowlisted CLI process with a signed operation token. Only loopback metering endpoints can authorize and record provider cost.
  </Step>

  <Step title="Settle the operation">
    Actual cost is debited and unused holds are returned when the manifest is sealed.
  </Step>
</Steps>

Measurement, research, recommendation generation, and SEO refresh jobs share one workspace job slot. A running job in any of those paths blocks a new measurement start until it settles or reconciliation marks it terminal.

## Lifecycle

The web job has these states:

| State                  | Meaning                                               |
| ---------------------- | ----------------------------------------------------- |
| <code>running</code>   | Process is alive or awaiting reconciliation           |
| <code>succeeded</code> | Process exited successfully and the operation settled |
| <code>failed</code>    | Launch, process, or reconciliation failed             |
| <code>cancelled</code> | An authorized user cancelled the process group        |

The underlying pipeline run can finish as <code>complete</code>, <code>partial</code>, or <code>failed</code>. A partial run can retain valid responses while recording provider failures.

<Note>
  If a recorded process ID is no longer alive, reconciliation moves the stale web job to failed and settles or releases its credit state.
</Note>

## Run detail

The detail page shows:

* Date, preset, status, duration, started time, and finished time
* Total provider cost and response count
* Per-engine successful, failed, and skipped responses
* Per-engine cost and average latency
* Prompt and response coverage
* Link to the frozen run report when one is available

Progress uses completed calls over expected calls when that total is known. Otherwise, log growth provides a limited progress signal.

## Cancellation

Cancellation requires approval in Chat or an authorized UI/API action. The worker terminates the process group, records the cancellation, and reconciles the reservation. A provider call already in flight may still produce a cost event.

## Troubleshooting

| Symptom                              | Check                                                           |
| ------------------------------------ | --------------------------------------------------------------- |
| Immediate provider failure           | Operator OpenRouter or Exa keys and preset engine access        |
| No eligible prompts                  | Active prompt count and archive state                           |
| Run stops before next call           | Credit balance, reservation, and lease status                   |
| One engine is absent                 | Preset membership, per-engine cap, and skipped response details |
| Job stays running after process exit | Job reconciliation and its private log                          |