Following a run

The run page — 03 Run — is both the live view and, once the run ends, the report. It refreshes itself every two seconds while the run is live and the tab is visible, and while a defect is being judged again. You can close the tab: the run keeps going, and the page shows where it got to when you come back. The app has no list of past runs yet, so keep the address.

The top of the page

A line such as Run 0001 · Live · app.example.com — the run’s number in the workspace, its status and the product’s host — and a headline:

Status	Headline
Queued	Waiting for a runner.
Live	Your people are using the product.
Complete	2 defects confirmed by replay., None of the reported defects was confirmed. or No defects found.
Stopped at cap	The same, starting with Stopped at the cap.
Cancelled	You stopped this run.
Failed	This run could not finish.

Below it, three figures:

• Live cost — dollars spent so far, with a bar of $2.00 cap. For a run with a token cap it shows Tokens so far against the 3 million tokens instead.
• Goals reached — for example 7 / 12: every person times every goal.
• Confirmed defects.

If the page loses its connection it says Lost contact with Trawler. Retrying…; the run itself is not affected.

Stages

Use, Replay, Judge, Report — each marked Waiting, In progress, Done or Skipped. Use is the people’s sessions. Replay and Judge begin only when every person has finished. Once the run has ended, a stage that never ran is Skipped — because the run ended first, or because there was nothing for it to do: a run with no defects has nothing to replay or judge. Judge shows In progress again while a defect is being judged again.

People

One card per person, with their state:

State	Meaning
Waiting	Their turn has not come yet.
Exploring	They are using the product now.
Goal reached	Their session ended with every goal reached.
Goal not reached	Their session ended with at least one goal failed.
Finished	Their session ended without failing a goal, but not every goal got a status.
Could not finish	Their session failed; the reason is shown in red. See Troubleshooting.
Stopped	The run ended before their turn came.

Each goal is listed under the person — ✓ reached, ✕ not reached, · no answer yet — with the person’s note about it, and, once they have reported something, a count of their defect reports and friction.

People take their turn one after another: a run works on one session at a time, so at most one card says Exploring. A person’s session ends when they finish, which they may do only once every goal has a status; after 60 steps; when the run stops; or when the session fails. A session cut short by the cap or by Stop ends as Finished or Goal not reached — or Goal reached, if it had already reached them all — with any goals it did not get to still open.

While the run is live, Latest lists the newest eight things that happened: notes the people wrote to themselves, findings as they are reported, goals reached or not, and the judge’s verdicts.

Stopping a run

Stop run at the bottom asks Stop now? What was found so far is kept. — choose Stop, or Keep running. Any member of the workspace can stop a run.

Stopping cancels everything still waiting. The session in progress stops the next time it reports in, and nothing after that is replayed or judged. Findings that had reached Trawler stay on the page; defects that were never replayed or judged appear under Not judged, and one whose judge was cut off under Could not be judged.

How a run ends

A run ends on its own when every session, replay and judge has finished — Complete, or Failed if every person’s session failed. It ends early as Stopped at cap when spending reaches the cap: what was still waiting is cancelled and the rest of the page reads as for a stopped run.

When it has ended, the bottom of the page names the model the run used and offers Start another run, which goes back to the plan.