Flow runs and approvals

Run history

A flow's Runs tab lists its own runs; All runs in the sidebar lists runs across the workspace, with a flow filter beside the status filter. Each row shows the trigger that started it, who started it (a person, a person through an API key, or an agent from a chat), when it started, how long it took and the credits it spent, or spent versus estimated while it is still going. The list refreshes itself for 30 minutes, then asks you to refresh.

Step detail

Open a run and the timeline lists every step in order: its status, how many attempts it took, its duration, credits, tool-call count, output size and a trace id for support. Steps on a branch that was not taken read Skipped; a step waiting on time reads Waiting until; a step waiting on a person reads Waiting for approval.

Select a step to open its detail sheet:

• Input — what the step received after templates were resolved.
• Output — what it produced and what later steps read as steps.<id>.output. A replayed run marks outputs it reused from the parent run. An output above 1 MB is not stored; the step fails and says so.
• Error — the failure code and message when the step failed.
• Tool calls — each call an agent turn made, with its arguments and result.
• Approval — the request, its approvers, deadline, and the decision with its note.

Every block has Copy JSON. Pin as test data keeps a step's output as the upstream input for tests in the builder, so you can iterate on the next step against a real result.

Open in chat seeds a conversation with the run summary and a preview of each step's output, so you can ask an agent what happened or carry on from the result. A run that an agent started from chat already has that thread; the button reads Continue chat.

Cancel and replay

1. Step 101

   Cancel a run

   Press Cancel run on a queued, waiting or running run and confirm. A queued or parked run is canceled at once; a running step stops at its next checkpoint. A finished run cannot be canceled.
2. Step 202

   Replay from a step

   Open any step, including the one that failed, and choose Replay from this step. Akili starts a new run on the same version with the same trigger input, copies the outputs of the steps before it that had succeeded, and executes from there. The new row says which run it was replayed from.
3. Step 303

   Run again from the builder

   Run starts the published version with a fresh input, and Fire once now on a trigger simulates that trigger firing. Both are real runs and count toward the daily limit.

Approvals

An approval step parks the run until a person decides. The step names its approvers (up to 20 members, or everyone holding a role, up to 50 people in all), an optional fallback person, a deadline from five minutes to 30 days, and the message approvers read. Approvers get an in-app notification when the request opens.

The approvals inbox

Approvals in the sidebar lists the requests addressed to you under Pending and the ones already decided under Decided. Each card shows the flow and step, when it was requested, the deadline or that it is overdue, the approvers or who it escalated to, and the message. Three buttons: Approve, Request changes and Reject; the last two ask for a note the flow owner reads. The run resumes the moment a decision is recorded and takes the edge for that outcome.

Approval cards in chat

When an agent started the run from a chat, or you opened the run in chat, a card in that conversation says a flow is waiting for approval, with the same three buttons and links to the run and the flow. The card is visible to the people who may decide; a reader who is not an approver sees a line saying only the named approvers can decide. Once decided, the card shows who decided, when, and the note.

Who may decide: the named approvers, holders of the named role, the fallback person, and anyone with the flows admin or approve permission. At the deadline the request escalates once to the fallback with a fresh deadline; after that it expires. A rejected, changes-requested or expired outcome needs an edge on the canvas, otherwise the run fails with that outcome as the reason.

Failures and auto-pause

A step fails when its executor errors after the retries you set (0 to 5 extra attempts, fixed or exponential backoff, two seconds between attempts by default), when it exceeds its timeout, when its credit cap is reached, when an agent turn's output does not match the output schema, or when its result is too large. Wire the step's failure handle, or the flow's error edge, to handle it; otherwise the run fails and, by default, the owner is notified.

• Consecutive failures. Three unattended runs failing in a row (schedule, webhook, event or agent-triggered; manual runs do not count) pause the flow. The owner gets a notification in the app, by email and by push; the Flows home shows Paused after repeated failures. Adjust the threshold from 0 (off) to 20 in the flow's Settings. A successful run resets the counter, and so does activating the flow again.
• Out of credits. An unattended run that fails for lack of credits pauses the flow with Paused: credits are low until you top up and activate it.
• Expired credentials. When an agent credential the flow depends on expires, the flow pauses and says so; reconnect the credential and activate.
• Run caps. A run that exceeds its credit cap or its timeout fails with that reason; waiting time and approvals do not count toward the timeout.

API and webhooks

Platform API keys, created under Settings, carry scopes. A key with no scopes keeps its owner's full access; a scoped key gets only what it names, and any write or run scope implies read. Keys are also subject to your organization's policy on API keys.

Start a manual run with POST /flows/:id/runs and a JSON body of { "input": { ... } } matching the flow's input schema; the answer carries the run id to poll with GET /flows/runs/:runId. A run started this way is listed as started by the key's owner via API key.

Outgoing webhooks

Organization webhooks, configured under Organization settings, can subscribe to flow events. Deliveries are signed with X-Akili-Signature: t=<unix>,v1=<HMAC-SHA256>, the same scheme an incoming webhook trigger expects from you.

Good to know

• Deep links. A notification opens the approval with /flows/approvals?id=…; if it is not in your inbox, it was decided already or belongs to someone else.
• Live updates. The run page follows a run as it executes. After 30 minutes it stops polling and shows a Refresh button.
• Parked runs. Runs waiting on time or approvals are capped at ten times your plan's concurrent-run limit; a step that would park one more fails fast instead of waiting.
• Mobile. The Akili app shows runs and run detail and lets you decide approvals from your phone.