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: Running

Goal

Add three items to the basket and stop before paying

Run id
run_3Kd
Started
Last change
Worker first connected
Task id
task_2vB7nM4t
Steps12 / 50
Deadline passes in 4mthis step 11s · total 6m 00s

Action replay

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

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.

  • openAppondev_pixel7_a19adb_real
    appId com.example.shop
    requested
    2026-09-03T11:14:36.000Z
    committed
    2026-09-03T11:14:36.820Z
    lease
    lease_QmT4vR
    fencing
    214
    frame
    frm_01_4c19
    agent:run_3Kd:f1:a17f3c
    Receipt status: Committed820 ms
  • tapondev_pixel7_a19adb_real
    x 512 · y 934
    requested
    2026-09-03T11:15:54.000Z
    committed
    2026-09-03T11:15:54.240Z
    lease
    lease_QmT4vR
    fencing
    215
    frame
    frm_04_77ab
    agent:run_3Kd:f4:b2e91d
    Receipt status: Committed240 ms
  • typeTextondev_pixel7_a19adb_real
    textLength 11 chars
    requested
    2026-09-03T11:17:00.000Z
    committed
    2026-09-03T11:17:01.310Z
    lease
    lease_QmT4vR
    fencing
    216
    frame
    frm_07_9d51
    agent:run_3Kd:f7:c88a02
    Receipt status: Committed1310 ms
  • swipeondev_pixel7_a19adb_real
    from 540, 1180 · to 540, 1180 · durationMs 900Shown exactly as the API recorded it: a swipe whose start and end are the same point. How this should read is still an open glossary question.
    Stale framestale_frame· retryable

    The frame this action bound to is older than the device's freshness window.

    The worker decided from an out-of-date frame. That is a worker-side problem, not a broken device.

    requested
    2026-09-03T11:18:00.000Z
    failed
    2026-09-03T11:18:00.060Z
    lease
    lease_QmT4vR
    fencing
    217
    frame
    frm_06_2f80
    agent:run_3Kd:f9:d41b77
    Receipt status: Failed60 ms
  • tapondev_pixel7_a19adb_real
    x 880 · y 1720
    requested
    2026-09-03T11:19:51.000Z
    lease
    lease_QmT4vR
    fencing
    218
    frame
    frm_11_bb14
    agent:run_3Kd:f11:e0c934
    Receipt status: Pending
    Sent, not yet confirmed
    waiting 9s