Skip to content

Run

What this run was asked to do, how it ended, and every action it dispatched. This link is permanent: the action trail is keyed on the run's id and outlives the run itself.

Data source
Run state: Needs takeover

Goal

Sign in with the test account and complete the SMS challenge

Run id
run_9wF
Started
Last change
Worker first connected
Task id
task_9wF1cD6y
Steps7 / 40
Deadline passes in 3mtotal 14m 00s

This run is waiting for a person

The worker handed control back and is waiting. The run's clock keeps running while it is parked and is capped by the lease it acts under, so a handoff that is not answered in time ends as a missed deadline rather than as a pause.

What the worker asked for

An SMS code was requested. Read it off the phone and enter it, then resume the run.

Action replay

Every action this run dispatched, oldest first, from GET /v1/receipts?agentRunId=run_9wF.

There are no pictures here. This is the sequence of actions, not a recording of the screen. The frame registry keeps a frame's identity and how fresh it was, never its pixels, so what can be replayed is what was asked of the device and how each request ended — the evidence trail, not the video.

No actions

No action receipts carry this run's id. Either the run took no actions, or it has not taken its first one yet.