Runs and live sessions
Every time a workflow runs, Tabductor opens a managed browser for it. You can watch that browser live, take the controls, and replay the recording afterwards.
The Runs tab
A workflow's Runs tab lists its runs, newest first, and refreshes every 2 seconds. Filter by status, or choose Older to page back. Each row has its actions at the end:
- Watch live while it runs, or View session after it ends, opens the run's browser session: the browser, every step the run took, and its result.
- Open browser appears when the run needs you.
- Cancel run stops a run that hasn't finished.
The Error column shows why a run failed. The editor shows how the latest run was done, “Ran with the AI agent” or “Ran distilled script v<n>”, and what the next run will use (see From agent to script).
Run statuses
| Status | Meaning |
|---|---|
| Queued | Waiting to start, for example while another run uses the same browser profile. |
| Running | The agent or the script is working in the browser. |
| Needs you | The run is paused on a step only a person can do. It keeps its browser open and waits. |
| Succeeded | The run finished and wrote its result. |
| Failed | The run stopped on an error. The run page says what happened. |
| Timed out | The run reached its time limit. |
| Cancelled | Someone cancelled it. |
Watching a session
Open a session from a run, or from Sessions, which lists every browser session in your account. The Control column says who is driving: Automation, You, API client or Paused.
While automation is in control you're watching live. To step in, choose Take control: you can click and type in the browser, and an address bar and the browser's tabs appear. Choose Resume automation to hand it back; the agent reads the page again before it continues. A takeover you start yourself hands control back after 10 minutes if you don't.
Anything that happens while a person has control is private: it isn't recorded.
When a run needs you
The agent solves most CAPTCHAs on its own. When it reaches something it can't do, such as a CAPTCHA the solver couldn't clear, a sign-in it has no details for, a verification code, or an approval, it pauses and asks for a person. The run shows Needs you and you get an email, “<workflow>: paused, needs you”, that says what happened and links to the browser.
- Open the run's browser from the email or the Runs tab.
- Choose Take control.
- Do the step: solve the CAPTCHA, sign in, or enter the code.
- Choose Resume automation. The run carries on from where it stopped.
The run waits for up to 30 minutes, and never past its own time limit. If no one resumes it in time, it fails saying a person was needed; run the workflow again when you're available. To avoid this for sign-ins, save them once in a profile. A webhook can also tell your own systems with the execution.needs_human event.
Replaying a session
After a session stops, its timeline becomes a slider over the recording. Drag it to scrub, or use the arrow keys (5 seconds), Page Up and Page Down (a minute), Home and End. The events list can follow playback or show everything; events outside the recording are listed under it. A gap in the recording is private activity or a moment that wasn't captured.
Stopping a session
Stop & save profile ends the session and saves the browser's sign-ins and storage to its profile. The recording becomes available for replay once the session has stopped.
How long runs are kept
- Run records (status, result, summary): until you delete the workflow or your account.
- Run detail (traces, screenshots, page content): 180 days after the run ends. After that the run reads “Details expired”, and its result is kept.
- Session recordings: 7 days after the session starts.
The privacy policy lists every retention period.