Agent job
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.
What you can do here
Section titled “What you can do here”- 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 screen at a glance
Section titled “The screen at a glance”

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
| Region | What it shows | What you do there |
|---|---|---|
| Header | Back, the job title, its status badge and Refresh | Return to the list, reload the job |
| Summary card | Trigger, owner, source, reason, tokens, cost, start and session | See where the job stands |
| Result | The final answer, for completed jobs | Read what the job produced |
| Steps | The plan, one row per step | Follow the plan |
| Approvals | Each approval the job asked for | See what waits for the customer |
| Events | The run’s events in order | Replay what happened |
Read the summary
Section titled “Read the summary”The card at the top sums up the job.
| Field | What it shows |
|---|---|
| Trigger | Webhook, Scheduled or Run now |
| Owner | The customer’s ID in your product, or — |
| Source | Where the run came from, such as Autonomous agent or Workflow |
| Reason | Why the job has its status, in English as recorded, such as the tool it waits to use or the error that stopped it |
| Tokens | Input and output tokens, once the job has finished |
| Cost | The estimated cost in US dollars with four decimals, once the job has finished |
| Started | When the job started |
| Session | The 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.
Follow the steps
Section titled “Follow the steps”The Steps table lists the plan the job made, one row per step, in order.
| Column | What it shows |
|---|---|
| Status | The step’s status, in English in every language: Pending, Running, WaitingForApproval, WaitingForInput, Completed, Failed, Skipped or Cancelled |
| Kind | The kind of step, in English: Plan, SubAgent, Tool, Approval, Clarify, Verify, Loop, Branch or Synthesis |
| Step | The step’s name |
| Attempts | Attempts so far out of the maximum, such as 1/3; for a loop step also “iteration … of …” |
| After | The step or steps it waits for |
| Last error | The last error, when the step failed |
Skippedmeans 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.
Check the approvals
Section titled “Check the approvals”The Approvals table lists every approval the job asked for.


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
| Column | What it shows |
|---|---|
| Status | Pending, Approved, Denied or Expired, in English in every language |
| Step | The step that needs the approval, with “Acts on: …” listing up to 8 records it would change, then ”+… more” |
| Tool | The tool the step wants to call |
| Risk | The tool’s risk level, in English |
| Requested | When the approval was requested |
| Decided by | Who 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.
Read the events
Section titled “Read the events”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 type | What the line describes |
|---|---|
JobStatus | The job’s new status and, when there is one, the reason |
SubAgentPlanReady | The sub-agents the plan will use |
ProgressStep | A step’s progress, such as a check that was confirmed |
JobApprovalRequired | The steps that now wait for approval |
StepTimedOut | A 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.
Every control, explained
Section titled “Every control, explained”The Back button at the top left.
Returns to AnalyticsAgent jobs, with no filters.
Go back to the list after checking one job.
Refresh
Section titled “Refresh”The Refresh button at the top right.
Loads the job again: summary, steps, approvals and events. The page does not update on its own.
See whether the job moved on after the customer decided an approval.
Result
Section titled “Result”The Result card below the summary, shown only for completed jobs.
The last answer the assistant wrote during the job, in full.
Read what the run produced without opening the conversation.
What you need to know
Section titled “What you need to know”| Topic | Fact |
|---|---|
| Read-only | Nothing on this page approves, answers or cancels a job. The customer decides in their portal. |
| English values | Step statuses, step kinds, approval statuses, risk levels, event types and the reason are shown in English in every language. |
| Cost and tokens | Added 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 history | The 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. |
| Times | Event times show the time of day only, in your browser’s format. |
| Who sees it | Every signed-in user of your workspace, whatever their role. |
Frequently asked questions
Section titled “Frequently asked questions”Reading the job
Section titled “Reading the job”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.
What does Skipped mean on a step?
Section titled “What does Skipped mean on a step?”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.
Why is there no Result?
Section titled “Why is there no Result?”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.
Approvals
Section titled “Approvals”Who decided an approval?
Section titled “Who decided an approval?”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.
Can I approve or cancel the job here?
Section titled “Can I approve or cancel the job here?”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.
What does Acts on mean?
Section titled “What does Acts on mean?”“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.
Troubleshooting
Section titled “Troubleshooting”| Symptom | What to check |
|---|---|
| The job stays Needs approval | Look at the Approvals table for Pending rows and ask the owning customer to decide in their portal. |
| The job is Failed | Read Reason and the Last error of the failed step. |
A step is Skipped | Check whether its approval was denied or expired, or whether a step in After failed. |
| The job is Paused | The 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. |