Skip to content

Agent job

For: Account owners and teams that run autonomous agents and scheduled workflowsRequires: Any signed-in user; no plan, role or feature flagScreenshots show sample data

The Agent job page shows one background run in full: what started it, whose it is, why it stopped or what it is waiting for, the steps of its plan, the approvals it asked for, the events it went through and, once completed, its result. Use it to understand what an autonomous agent or scheduled workflow actually did. You open it with the eye icon on AnalyticsAgent jobs; the heading is the job’s title with its status badge. Everyone in your workspace can open it, and it only reads: approvals are decided by the customer in their portal.

  • See where the job stands and why. The summary card gives the trigger, owner, source, the reason for its status, tokens, cost and start time. Read the summary.
  • Follow the plan. The steps table lists every step with its kind, status, attempts and the step it runs after. Follow the steps.
  • See what waits for approval. The approvals table shows each tool call that needed the customer’s decision, the records it acts on, its risk and who decided. Check the approvals.
  • Replay what happened. The events list records the run in order, from start to finish. Read the events.
The detail page of the agent job "Autonomous: Overdue invoice follow-up 9/15 06:46" with a red "Needs approval" badge, "Back" and "Refresh". The summary card shows trigger Webhook, owner cus_48321, source Autonomous agent, the reason "parked on 1 sub-agent approval(s)", the start time and the session id; cost and tokens stay empty until the run finishes. The highlighted "Steps" table lists plan, check_invoice and check_payment_methods as Completed and send_reminder as WaitingForApproval, each with kind, attempt 1/3 and the steps it runs after.The detail page of the agent job "Autonomous: Overdue invoice follow-up 9/15 06:46" with a red "Needs approval" badge, "Back" and "Refresh". The summary card shows trigger Webhook, owner cus_48321, source Autonomous agent, the reason "parked on 1 sub-agent approval(s)", the start time and the session id; cost and tokens stay empty until the run finishes. The highlighted "Steps" table lists plan, check_invoice and check_payment_methods as Completed and send_reminder as WaitingForApproval, each with kind, attempt 1/3 and the steps it runs after.
The job page shows why a run is parked and which step it reached; finished steps are marked Completed.
What this screenshot shows
Screen
Agent job (/admin/agent-jobs/:id)
Highlighted
“”, steps-table, 4 steps, last waiting for approval. lists the plan steps and their status
Also visible
Summary: Webhook, cus_48321, Autonomous agent, reason parked on 1 sub-agent approval(s); Steps plan, check_invoice, check_payment_methods Completed; send_reminder WaitingForApproval
Purpose
the job page as it opens
RegionWhat it showsWhat you do there
HeaderBack, the job title, its status badge and RefreshReturn to the list, reload the job
Summary cardTrigger, owner, source, reason, tokens, cost, start and sessionSee where the job stands
ResultThe final answer, for completed jobsRead what the job produced
StepsThe plan, one row per stepFollow the plan
ApprovalsEach approval the job asked forSee what waits for the customer
EventsThe run’s events in orderReplay what happened

The card at the top sums up the job.

FieldWhat it shows
TriggerWebhook, Scheduled or Run now
OwnerThe customer’s ID in your product, or —
SourceWhere the run came from, such as Autonomous agent or Workflow
ReasonWhy the job has its status, in English as recorded, such as the tool it waits to use or the error that stopped it
TokensInput and output tokens, once the job has finished
CostThe estimated cost in US dollars with four decimals, once the job has finished
StartedWhen the job started
SessionThe ID of the conversation the run used, as plain text

When the job is Paused because of the AI allowance, the reason reads Paused — the AI allowance for this period is used up; the run continues when it resets or the limit is raised.

Example: a webhook started the Billing Assistant for a customer. The badge shows Needs approval, and Reason names the tool it waits to use, a tool that issues credit notes. Tokens and cost are still empty because the job has not finished.

The Steps table lists the plan the job made, one row per step, in order.

ColumnWhat it shows
StatusThe step’s status, in English in every language: Pending, Running, WaitingForApproval, WaitingForInput, Completed, Failed, Skipped or Cancelled
KindThe kind of step, in English: Plan, SubAgent, Tool, Approval, Clarify, Verify, Loop, Branch or Synthesis
StepThe step’s name
AttemptsAttempts so far out of the maximum, such as 1/3; for a loop step also “iteration … of …”
AfterThe step or steps it waits for
Last errorThe last error, when the step failed
  • Skipped means the step never ran, because its approval was denied or missing, or a step it depends on failed.
  • A loop step repeats up to a set number of iterations, 3 unless the workflow sets another number.

The Approvals table lists every approval the job asked for.

The lower part of the same agent job page. The highlighted "Approvals" table has one Pending row for the step send_reminder, "Acts on: INV-2026-0451", tool resendInvoice, risk Medium, the time it was requested and no one in "Decided by" yet. Below, "Events" lists the run in order: JobStatus Running, SubAgentPlanReady, the ProgressSteps "INV-2026-0451 is 22 days overdue (GBP 640.00)" and "Visa ending 4417 is on file (expires 03/2027)", JobApprovalRequired and JobStatus WaitingForApproval.The lower part of the same agent job page. The highlighted "Approvals" table has one Pending row for the step send_reminder, "Acts on: INV-2026-0451", tool resendInvoice, risk Medium, the time it was requested and no one in "Decided by" yet. Below, "Events" lists the run in order: JobStatus Running, SubAgentPlanReady, the ProgressSteps "INV-2026-0451 is 22 days overdue (GBP 640.00)" and "Visa ending 4417 is on file (expires 03/2027)", JobApprovalRequired and JobStatus WaitingForApproval.
Approvals shows which tool call waits for the customer and what it acts on; Events records each step of the run.
What this screenshot shows
Screen
Agent job (/admin/agent-jobs/:id)
Highlighted
“”, approvals-table, one Pending approval. lists approvals requested by the run
Also visible
Approval: send_reminder, resendInvoice, Medium, Acts on INV-2026-0451; Events: six entries from Running to WaitingForApproval
Purpose
what the run is waiting for and what happened so far
ColumnWhat it shows
StatusPending, Approved, Denied or Expired, in English in every language
StepThe step that needs the approval, with “Acts on: …” listing up to 8 records it would change, then ”+… more”
ToolThe tool the step wants to call
RiskThe tool’s risk level, in English
RequestedWhen the approval was requested
Decided byWho decided, empty while pending

The customer who owns the job decides in their customer portal. An approved tool call runs and the job continues; a denied one is skipped. An approval nobody decides before it expires becomes Expired: the step fails, the job does not fail because of it.

The Events list records the run in order, oldest first, in a scrolling box. Each line shows the time (without the date), the event type in English and a one-line description.

Event typeWhat the line describes
JobStatusThe job’s new status and, when there is one, the reason
SubAgentPlanReadyThe sub-agents the plan will use
ProgressStepA step’s progress, such as a check that was confirmed
JobApprovalRequiredThe steps that now wait for approval
StepTimedOutA step that ran out of time
  • Other event types are not shown on this page.
  • The list shows the first 200 events of a job. For a very long run, the most recent events are not in the list.
  • Events of a finished job are deleted once they are more than 7 days old. The job, its steps and approvals stay; the events section is then empty or missing.
Where

The Back button at the top left.

What

Returns to AnalyticsAgent jobs, with no filters.

Why

Go back to the list after checking one job.

Where

The Refresh button at the top right.

What

Loads the job again: summary, steps, approvals and events. The page does not update on its own.

Why

See whether the job moved on after the customer decided an approval.

Where

The Result card below the summary, shown only for completed jobs.

What

The last answer the assistant wrote during the job, in full.

Why

Read what the run produced without opening the conversation.

TopicFact
Read-onlyNothing on this page approves, answers or cancels a job. The customer decides in their portal.
English valuesStep statuses, step kinds, approval statuses, risk levels, event types and the reason are shown in English in every language.
Cost and tokensAdded up from the job’s calls to AI models when the job finishes; open jobs show nothing. Calls without a price count as 0.
Event historyThe first 200 events are shown, oldest first. Events of a finished job are deleted once they are more than 7 days old; this is the only automatic deletion in Analytics.
TimesEvent times show the time of day only, in your browser’s format.
Who sees itEvery signed-in user of your workspace, whatever their role.

Why is the events list empty for an older job?

Section titled “Why is the events list empty for an older job?”

Events of a finished job are deleted once they are more than 7 days old. The job’s summary, steps and approvals on Agent job stay, but the Events section is empty or not shown.

Skipped in the Steps table means the step never ran: the customer denied its approval, the approval was missing, or a step it depends on failed. The other steps of the job can still complete.

The Result card appears only when the job is Completed and the assistant wrote a reply during the run. Open, failed and cancelled jobs show no result; read Reason and the steps instead.

Why are statuses and step kinds in English?

Section titled “Why are statuses and step kinds in English?”

The Steps and Approvals tables show step statuses, step kinds, approval statuses and risk levels as the product records them, in English in every language. Only the job’s own status badge is translated.

Why don’t I see the latest events of a long run?

Section titled “Why don’t I see the latest events of a long run?”

The Events list on Agent job shows the first 200 events of a job, oldest first. For a run with more events, the most recent ones are left out; the status badge and the steps still show where the job stands now.

Decided by in the Approvals table names who made the decision. It stays empty while the approval is Pending, and for an approval that expired without a decision.

No. Agent job only reads. The customer who owns the job approves or denies its tool calls in their customer portal; select Refresh afterwards to see the job continue.

“Acts on: …” under a step in the Approvals table lists the records the tool call would change, such as invoice numbers. Up to 8 are listed, then ”+… more”, so the customer and your team can see exactly what an approval allows.

SymptomWhat to check
The job stays Needs approvalLook at the Approvals table for Pending rows and ask the owning customer to decide in their portal.
The job is FailedRead Reason and the Last error of the failed step.
A step is SkippedCheck whether its approval was denied or expired, or whether a step in After failed.
The job is PausedThe AI allowance is used up. Raise the limit under ConfigureBudgets & limits or wait for the period to reset.
Failed to load agent jobs or “Job not found”The job may not exist or the link is wrong. Go Back and open it from the list.