Run Detail: Live Stream, Interrupt, and Transcripts

The run detail page is the forensic view of a single run — and, while the run is still going, your live control panel. You land here automatically when you click Run now on an automation, or open any row in Run History.

The header and key facts

The header shows the run's short id, a status badge, the trigger, and when it started. Below it, a Key facts grid gives the numbers you scan first:

• Duration — how long the run took (its metered active time when available, otherwise the wall-clock span).
• Tool calls — how many tools the run invoked.
• Credits — credits consumed, shown to two decimal places.
• Tokens — total input + output tokens, with an input / output sub-line; hover for the cache-read and cache-write breakdown.

A couple of context notes can appear here too: if StackJack staff started the run on your behalf, an info note says so and that no credits were charged to your account; if the run was automatically restarted after a service interruption, a line notes that the original credit hold was reused, so you were billed once.

While a run is still in progress the page updates itself — the status badge, the key facts, and (once the run finishes) the summary all refresh on their own, so you don't have to reload the page or navigate away to see the final outcome.

Tool sequence

When a run has made (or, in a dry run, would have made) tool calls, a Tool sequence card lists them in the order they ran. Select one or more and choose Allow, Require, or Deny to add them to this automation's tool policy, or To chain to capture them as an ordered chain — each opens the advanced builder with your selection staged.

Summary, errors, and timing

• Summary — when the agent produced a final summary of what it did, it appears in its own card.
• Error — if the run recorded an error, it is shown in a red banner (a failed run says it "failed"; a run that merely reported an error says so).
• Timing — a card near the bottom lists when the run was Created, Started, and Completed, plus Active time (the time the AI session was actually working, which also feeds runtime billing).
• Trigger payload — shown when the run was started with input: your Run with message… text, an AI-assistant-supplied message, or the (filtered) body of a webhook delivery.

Watching a running run (live stream)

While a run's status is Running, a Live stream card appears:

1. The stream starts on its own when you open a running run — you don't have to click anything to begin watching. (This holds even if you arrive while the run is still queued: it starts streaming the moment the run flips to Running.)
2. Events render as a live conversation timeline — the same view as the transcript below: assistant and user turns, collapsible thinking blocks, and each tool call paired with its result as a collapsible card marked ok or error.
3. Click Pause to stop consuming the stream (the run itself keeps going); Start stream resumes watching.

Interrupting a run

The Interrupt button (in the Live stream card) stops a running run:

• The run is durably marked Interrupted first, then the execution is cancelled — an interrupt is never silently lost.
• Credits are settled from actual usage: whatever portion of the run's credit reservation went unused is refunded.
• Interrupted runs stay in run history with their status and usage intact.

Paused runs and tool approvals

Automations must currently be configured so the agent can use its allowed tools without asking a person — there is no approve/deny step in a run. If the agent hits a tool call that requires human confirmation, the run does not wait indefinitely for input; it fails with guidance to adjust the automation's tool policy so the tool is auto-allowed.

If you ever see a run in the Awaiting input status, the page shows a warning explaining that the run is paused for tool approval and that the Approve/Deny controls are not available in the portal — contact support, or adjust the automation's tool policy to auto-allow the tool.

Transcripts

If the run reached an AI session, a Transcript card appears at the bottom.

Privacy first: transcripts are not stored by StackJack — they may contain your customers' data from the run's tool calls. Nothing is fetched until you ask.

1. Click View transcript. The conversation is fetched on demand from Anthropic and rendered as a timeline.
2. The timeline shows assistant and user turns, collapsible thinking blocks, and each tool call paired with its result as a collapsible card marked ok or error. Expand a tool call to see its arguments and result, each with a copy button. A Conversation / Raw JSON toggle switches to the raw event stream, and Download saves the raw JSON.
3. Long transcripts are windowed — Show more reveals the next 250 events, and Load more events fetches the next page from Anthropic when one exists.
4. Click Refresh to re-fetch (useful right after a run completes).

If the fetch fails you'll see one of: SJ-TRANSCRIPT-FORBIDDEN (access denied), SJ-TRANSCRIPT-NOT-FOUND, SJ-TRANSCRIPT-UNAVAILABLE (couldn't reach the automation service), or SJ-TRANSCRIPT-ERROR (other failure).

Page-load errors

SJ-AGENT-FORBIDDEN (your tenant may not view this run), SJ-RUN-NOT-FOUND (the run does not exist), SJ-AGENT-UNAVAILABLE (transient — retry), SJ-AGENT-SERVER-ERROR (retry, then contact support).