Before you start
- A role that can read agent runs (the
runs.readpermission). Without it, Activity is not in the Ankra AI menu, and an agent task link reads Your role cannot read agent runs. - Organisation admin access and permission to operate runs, to stop a run. Without them, Stop run is greyed out and the run page reads Stopping a run requires organisation admin access and permission to operate runs.
1. Find the run
- Portal
- CLI
- MCP
Open Ankra AI → Activity (
/next/ai/agent-runs). Agent runs lists the latest runs, newest first, with each run’s Task, Status, Environment, Duration and when it Started.Narrow the list:- Run views: All runs, Active, Needs review, Waiting for a person, Failed or Completed, each with its count.
- Environment for one cluster, Run state for one status, and Search loaded runs for a task name, a ticket number or text in the outcome.
- a ticket’s Work tab, under Agent runs, with View run details;
- Ankra AI → Overview, under Recent agent results;
- a link in a pull request comment, a check run or a notification. Such a link opens the agent’s newest run. Until the agent has run, it reads This agent task has not run yet and checks again every few seconds.
2. Read what it did
The run’s page names its agent as Ankra agent, says when it started, and opens with what the run came to:
A run can also read Cancelled, Expired or Skipped.
Below it, Run activity shows each step as Readable activity: what the Ankra agent wrote, each Tool activity, each User message and each Platform observation. Technical view shows the same record as JSON. The activity refreshes on its own while you watch, and Load more activity reads further.
Run details beside it gives the Agent, Task, Environment, linked Ticket and its Ticket owner, the Duration (for a live run, the time since it started, including any wait), Turns recorded and Tool calls. Record identity holds the run’s id, its task id and its recorded status.
- CLI
- MCP
ankra agents run prints the run in full: its agent, status, start and finish, goal status, session, trigger, outcome and turns. ankra agents transcript reads its session transcript; --since <sequence> returns only the events after one you have read.3. Answer what it waits for
A run that reads Waiting for a person resumes once a person answers. Where you answer depends on what it waits for:- A plan - Review change opens the plan on its ticket. See Plans, review and approval.
- A choice - Open ticket opens the ticket on the agent’s question. Pick an option and press Send decision to Ankra. See Answering a choice.
- A production change - the change waits under Proposed production changes on the ticket, and in Needs you.
- A failed run - Open ticket to steer the next step opens its ticket. A comment under Add context wakes the agent with your instructions.
4. Stop it
Stopping a run stops its next activity. Work it has already done is not undone, and its ticket stays open.- Portal
- CLI
- MCP
- On the run’s page, press Stop run. It shows only while the run is queued, running or waiting for a person.
- Read Stop this run? and press Stop run, or Keep running to leave it.
Verify
Open Ankra AI → Activity and choose Active. A run you stopped is no longer in that view; under All runs it reads Cancelled. From the CLI,ankra agents run <run-id> prints Status: cancelled.
What can go wrong
Next steps
- AI agents - the agents behind runs, and how to pause one
- Set up the ticket desk - tickets the Ankra agent works
- Watch for a problem - investigations that run when an alert fires