Monitor Agent Sessions

Agent Sessions is where you monitor agent activity. When a session starts, it appears here. Use Agent Sessions to understand what an agent did and why, diagnose failures, and intervene by pausing or canceling sessions when needed.

Sessions aren’t started in Agent Sessions. You can start a session several ways:

Save and Run from the agent configuration page in Agent Projects > Agent Builder. This starts a session immediately and opens the session detail in a new tab. For more information, see Create and run agents.
A trigger in Operations Manager - Manual, schedule, API, and event triggers are all supported. For more information, see Create agents in Operations Manager.
A workflow - A workflow that includes a Run Agent task in Studio starts a session when it reaches that task. For more information, see runAgent.
Another agent - An agent can call this agent as a tool, which starts a new session. For more information, see Called agents and workflows.

Before you begin

Before you begin, make sure you have the following:

Your admin has granted you access to Agent Sessions in Admin Essentials. Opening the page and viewing session data use separate permissions; without the page role, Agent Sessions doesn’t appear in your navigation. For more information, see Access control.
At least one agent has run. Sessions appear here only after an agent starts. For more information, see Create and run agents.

Access Agent Sessions

Agent Sessions is available in the Platform app. If Agent Sessions doesn’t appear in your navigation, contact your Platform administrator.

Session list

The session list shows all agent sessions, across all statuses. Itential sorts sessions by start time descending by default, with the most recent session first.

Each session row shows a Trigger Type and a Source. Together they answer why a session started and who or what initiated it.

Trigger Type	Source shows
Manual	Name of the person who ran the session
API	Name of the service account used to call the API
Event	Name of the event that fired
Schedule	Cadence of the schedule that ran
Agent	Name of the calling agent
Job	Name of the calling workflow

API, event, and schedule sessions originate from triggers configured in Operations Manager. You start a manual session yourself, either by clicking Save and Run in Agent Builder or by running a manual trigger in Operations Manager. Agent and job sessions are started programmatically: by another agent that called this one as a tool, or by a workflow that includes a Run Agent task. These appear in the list as their own entries, with the calling agent or workflow as the source.

Quick actions - Each session row includes quick actions based on the current session status. You can also select multiple sessions and apply bulk actions. When a mix of statuses is selected, only the actions valid for all selected sessions are available.

Status	Available actions
`Running`	Pause, Cancel
`Pausing`	None (waiting to transition)
`Paused`	Resume, Cancel
`Canceling`	None (waiting to transition)
`Completed`	Delete
`Failed`	Delete
`Canceled`	Delete

Session statuses

A session moves through the following statuses during its lifecycle. Pausing and Canceling are transitional states because pause and cancel are asynchronous. The agent must finish any in-flight tool call before reaching the target state.

Status	Description
Running	The agent is running: reasoning, dispatching tool calls.
Pausing	A pause was initiated. No new tool calls will start. Waiting for in-flight calls to finish.
Paused	The agent is halted. Can be resumed or canceled.
Canceling	A cancel was initiated. No new tool calls will start. In-flight tool calls finish on their own.
Canceled	The agent is permanently stopped. Can’t be resumed.
Completed	The agent finished and returned a response.
Failed	The agent encountered an unrecoverable error.

Session detail

Click any session row to open its detail view.

Summary

The Summary section shows the resolved prompt the agent received, including any input variable values substituted at runtime.

Agent Activity

Agent Activity displays the agent’s full trace in chronological order: reasoning steps, tool calls, and the final response. Use the filter tabs to focus on reasoning only or tool calls only.

Tool call entries - Each tool call resolves to one of the following states:

State	Behavior
Succeeded	Result is available to expand. Results above the payload size threshold are download-only.
Failed	Shows the error category and message. If the tool was retried, the retry count is shown.
Canceled	Resolved with duration when the session was canceled mid-call.

When a tool call invokes a manual task, the session waits indefinitely for human action before it can continue; it won’t time out on its own. The tool call entry in Agent Activity shows a link to complete the task in Work Center. Work Center is a dedicated interface for completing manual tasks from both agent sessions and workflow jobs, so you can act on a task without tracing how it was started. After you submit the task in Work Center, the session automatically resumes. If the session is canceled before the task is completed, the tool call resolves as Canceled.

When a tool call started an agent session or workflow job, the entry includes a link to that session or job.

Pause and resume events - Pause and resume actions appear as interleaved entries in Agent Activity, so the complete trace, including interventions, is visible in one view.

Pause a session

Pausing stops the agent from starting new tool calls. Any tool calls already in flight finish normally. A paused session can be resumed or canceled.

From the session list or session detail, click Pause.

Confirm the pause in the dialog. The session transitions to Pausing, then to Paused once in-flight tool calls complete.

To resume a paused session, click Resume from the session list, the session detail header, or the inline system entry in the feed.

Cancel a session

Canceling permanently stops a session. The session can’t be resumed. The agent stops dispatching new tool calls immediately. Any tool calls already in flight finish on their own. Canceling a session doesn’t cancel any agent sessions or workflow jobs it has already started.

From the session list or session detail, click Cancel.

Confirm in the dialog. This action is irreversible. The session transitions to Canceling, then to Canceled once the agent stops dispatching tool calls.

Delete a session

Delete is available for sessions in a terminal state: Completed, Failed, or Canceled. Deletion is permanent and removes the session record and its audit trail. This is an admin-level action.

Deleting a session permanently removes the session record and can’t be undone.

Called agents and workflows

When an agent calls another agent or a workflow, the called session or job appears in Agent Activity as a tool call entry. How much detail you see depends on your access:

Called session or job	What you see
Called agent session (you have access)	Full session detail (reasoning, tool calls, payloads) and a link to open the called session in its own detail view.
Called agent session (you don’t have access)	Metadata only: session name, status, and timestamps. No payloads or reasoning.
Called workflow job (you have Ops Manager access)	Metadata in the feed and a link to Operations Manager for the full job detail.
Called workflow job (you don’t have Ops Manager access)	Metadata only: job name, status, and timestamps.

Run Agent task in Studio

The Run Agent Studio task invokes an agent from a workflow canvas, letting you combine deterministic workflow logic with an agent’s dynamic reasoning. For configuration and output details, see runAgent.

Access control

Each Agent Sessions action requires an application-level permission. An admin assigns these permissions in Admin Essentials → Authorization on-prem, or through Cloud Hub role management on cloud.

Pausing, canceling, and deleting also require read access. Session visibility is retroactive: if your admin grants you access after sessions have already run, those historical sessions become visible. For the full list of permissions, see FlowAI roles.