Trajectory View and Stop

A trajectory is a unit that groups the transactions participating in one LLM workflow by mtid. Even if multiple transactions are grouped or the flow passes through multiple processes, it is treated as one trajectory.

This document describes how to check running trajectories in the list and the execution flow chart, and how to stop a problematic trajectory from the screen.

Note

Stopping a trajectory is available in Python SDK 2.2.1 or later. The Java SDK does not support stopping.

How to access

Screen	How to open
Active Trajectory list	In the Active Trajectory widget of the Overview Dashboard or the AI Agent Main Dashboard, click the orbit chart (full list), a level row (list for that level), or the Details icon in the header (full list). It can be opened only when the dashboard is in real-time mode, and levels with a count of 0 cannot be clicked.
Trajectory view	Click a group header or transaction row in the Active Trajectory list, or select a call in the running call list of the Active LLM API widget.
Trajectory View tab	In the LLM trace details, select the Trajectory View tab. It shows the trajectory that the transaction belongs to.

The list and view opened from the dashboard open as a window (modal). Click the Open in new window button in the window header to open it in a separate window. A list filtered by level opens with the same level in the separate window as well. When you select a trajectory in a list opened in a separate window, the same window switches to the trajectory view, and clicking the Back button returns to the list.

Active Trajectory list

This list shows currently running transactions grouped by trajectory. The window title is "Active Trajectory".

• Above the list are the number of trajectories and transactions, the CSV download button, and a search field (name / user / session). The search term is matched against the transaction name, user, session, and mtid.

• Each trajectory has a group header, and the transactions grouped under it are shown as rows. Click a group header or transaction row to open the trajectory view for that trajectory.

• The list opens sorted by the total number of steps per trajectory, in descending order. Up to 100 transactions are queried.

• Only running transactions are shown. Finished transactions are removed from the list.

Group header

Item	Description
Level	Light, Middle, Heavy. A level assigned to the entire trajectory; it does not indicate speed or execution time. Level boundaries follow the criteria set in the SDK options. If there is no level information, Unknown is shown.
mtid	Key that groups a trajectory. A standalone flow without an mtid is shown as "Standalone run".
tx N	Number of grouped transactions. If filtered by search, the number of remaining transactions.
User, Session	user_id and session_id attached to the log. If there is no value, - is shown.
Stop	Stops the trajectory. See Stopping a trajectory.

Transaction row

Column	Description
Transaction	Transaction name. The original name including prefixes such as [Workflow] and [Agent].
Steps	Number of steps the transaction performed
Agent	Number of AI subagents the transaction ran. If none, - is shown.
LLM Calls	Number of LLM calls that occurred within the transaction
Elapsed	Time elapsed since the transaction started

Note

In addition to the columns on the screen, the CSV file includes the Status, mtid, User, and Session columns for each row. The Status value is not the progress status but the level (Light, Middle, Heavy, Unknown) of the trajectory that the transaction belongs to.

Time control

The list opens paused at the time it was opened. This keeps the sort order from changing while you read the list.

• Click the play button to refresh the list at the configured interval. Click it again to pause at that point.

• Click the refresh button to refresh once to the current time.

• Click the settings button and change the Auto refresh (sec) value to set the refresh interval to 10 to 30 seconds (in 5-second steps, default 10 seconds).

Trajectory view

This screen shows the execution flow of one trajectory as a chart. The window title is "Trajectory View".

• Top tools: Project selection and time control. In project selection, you can choose AI Agent Observability projects to query along with the current project. Like the list, the time control opens paused at the time it was opened. When the trajectory finishes, time selection and refresh interval settings are disabled, and a Completed or Failed tag is added.

• Header: Root transaction name, status tag (Running, Completed, Failed), and the Stop button.

• Info line: Shows mtid (standalone run if none), user, session, and elapsed time. User and session are shown only when they have values.

Execution flow chart

• The vertical axis is time, and the horizontal axis is delegation depth. Long idle periods are collapsed.

• Each card is one transaction. A card shows the type (WORKFLOW, AGENT, LLM API), name, elapsed time, number of steps, and status (Running, Completed, Error, Not collected). Transactions without a type tag are also shown as AGENT.

• If 4 or more transactions under the same parent start at the same time or run in sequence, or if sub-delegation continues for 4 or more levels, only the first 3 are shown as cards and the rest are collapsed into "+N · Concurrent", "+N · Sequential", or "+N · Sub-delegation" tiles. Click a tile to expand it, and click "Transactions N · Collapse" to collapse it again.

• If a parent transaction was not collected, a "(Not collected)" card is shown in its place. If some child transactions are omitted from the query result, a "+N not shown" card is shown under the parent.

• If the trajectory cannot be found, "Trajectory not found." is shown.

• For a trajectory that has already finished, a View Transaction button is shown instead of the chart. Click it to open the LLM trace details. The Trajectory View tab of the LLM trace details shows finished trajectories as a chart as well.

Step details

Click a card in the chart to open the step details of that transaction on the right. While the details are open, you can still click or scroll the chart behind it.

• For a running transaction, only the Table View tab is shown, and "Running" appears in the last row. The content reflects the moment you clicked the card and is not refreshed automatically.

• To keep following the progress, click the Open in new window button in the details header. The "Trajectory Details" window opens, and you can refresh it with its time control.

• For a finished transaction, the Record Summary and Table View tabs are shown, as in the LLM trace details.

• In the Table View, LLM API steps also show the prompt change compared to the previous call (prompt delta). For more information, see Prompt Delta.

Stopping a trajectory

You can stop a running trajectory from the screen. Use it to cut off a flow whose cost keeps growing due to repeated calls, or a flow started by an incorrect request. A stop is requested per trajectory, and the running transactions of that trajectory shown on the screen are the stop targets.

Scope of a stop

• Running LLM calls are cut off, and the transactions are terminated.

• Subsequent LLM calls in the same trajectory are also blocked.

• The stop point is recorded in the transaction trace as a message step WhaTap: LLM trajectory stopped by control, so you can distinguish it from application errors. Check it in the Table View of the LLM trace details.

Caution

A stop cannot be undone. Check the target trajectory and the number of transactions in the confirmation window before running it.

How to stop

1. Click the Stop button in one of the following places.

   • Active Trajectory list: right end of the trajectory group header

   • Trajectory view: right end of the title line

   • Trajectory View tab of the LLM trace details: right end of the title line (when the same trajectory has running transactions)

2. In the "Stop Trajectory" confirmation window, check the target name and mtid · tx N. N is the number of transactions to which the stop request will actually be sent.

3. Enter the Secret Key. Click the eye icon to check the entered key.

4. Click Stop. You can also press Enter in the input field.

5. Regardless of the result, the window closes and a result message appears at the top of the screen.

The running call list of the Active LLM API widget has no Stop button. Select a call in the list to move to the trajectory view, and then stop it there.

Result messages

Result	Message	Meaning and action
Success	Success	All targets accepted the stop or are already stopping.
Not confirmed	Stop was requested, but the SDK did not confirm it. Refresh the list to check.	The request was delivered to the SDK, but there was no response within 3 seconds. It may actually have stopped, and retrying is safe. The Java SDK always shows this message.
Key error	The security key is invalid.	The SDK rejected the secret key. Check the key and try again.
No target	There are no active transactions.	The SDK has no target transaction. The transaction may have finished in the meantime.
Delivery failure	The stop request could not be sent because the SDK is not connected. Check the SDK status and try again.	The request was not delivered to the SDK, so nothing was stopped. Check the SDK status and try again.
Other failure	An unknown error occurred.	The server rejected the request, an exception occurred in the SDK, or the request did not reach the server.

• Except when the server rejected the request or the request did not reach the server, failure and warning messages end with the application name in parentheses.

• If there are multiple targets, only the worst result is shown. If only some targets were stopped, the result is not shown as success.

When the Stop button is hidden or disabled

State	Cause
Button not shown	It is a standalone flow without an mtid (standalone run), or there are no running member transactions.
Button disabled (gray)	You do not have edit permission for the current project. Hovering over the button shows "You do not have edit permission."

Notes

• If you stop while the list is filtered by a search term, only the transactions remaining on the screen are targeted.

• If you selected multiple projects together in the trajectory view, stop requests are sent separately per project. If any of them is rejected, "An unknown error occurred." is shown even if the other requests were accepted.

• Because the SDK processes stops asynchronously, the trajectory may not disappear from the list or view immediately even after a successful stop.

• A stopped trajectory has no separate "Stopped" status. It is shown as Completed or Failed afterward, so check whether it was stopped with the message step in the LLM trace details.

Reference: Difference from user blocking

User blocking, which blocks LLM calls from specific users, is also supported in Python SDK 2.2.1 or later. The two features differ in target, timing, and behavior.

Category	Trajectory stop	User blocking
Target	One running trajectory	All LLM calls from the specified user IDs
Method	Stop button on the screen	SDK option llm_blocked_users
Timing	Cuts off a running flow after the fact	Blocks before the call
Behavior	Cuts off running LLM calls, terminates the transactions, and blocks subsequent LLM calls in the same trajectory	Blocks LLM calls from the user and returns a connection error of the LLM client library (e.g., APIConnectionError)
Trace record	WhaTap: LLM trajectory stopped by control	WhaTap: LLM call blocked for user …

For user blocking settings, see Python SDK settings.