How to View Agent Team Runs and Results in GTM One

Learn how to review what your agent team produced each time it ran.

Overview

Each time an agent team runs, GTM One keeps a record of the run: its status, the inputs it was given and the output of every step. You can review runs from the agent team itself. A single run has its own output view, and a batch of runs started together has its own view.

View the runs and results of an agent team

1. Open the agent team whose runs you want to review.
2. Go to the agent team's runs, which are listed in a table with one row per run.
3. Find the run you want in the table and check its status tag, its inputs and its output columns.
4. Select a single run to open its output and read the result of each step in order.
5. Select a batch run to open the batch and review the runs it contains.

Reading the output columns

The runs table has one output column for each step of the agent team. The column header names the step by its position:

• Output: Step 1 is the first top-level step.
• Output: Step 2 Conditional routing is a step that routes the run down one of several condition paths.
• Output: Step 2/Condition 1/Step 1 is the first step on the first condition path of step 2.
• Output: Step 3.1 is the first step inside step 3, where step 3 repeats its steps for each item in a list.

For a conditional routing step, the column shows the path the run took. Steps on a path the run did not take are shown as not run and have no output.

For a step that repeats for each item in a list, the runs table shows the output for the first item only. Open the run to see the output for every item.

Reading a single run

The output of a single run lists each step with its result:

• A conditional routing step shows the condition that was met (e.g., "Condition 1:" followed by the condition), or "Default path taken - no conditions met" when none of the conditions were met.
• A step that repeats for each item lists one entry per item, numbered "#1", "#2" and so on, followed by the item's name when it has one.
• A step that produced nothing shows "No output available".

Run inputs and how a run started

The inputs a run was given are shown with the run. When a CSV file was provided as an input, it is labeled "CSV file" and only the file name is shown. Each run also shows whether it was started manually or by a trigger. When a run was started for a whole audience, the run shows the name of the audience.

Run statuses

Each run carries a status tag. A run can be queued, running, completed, completed with failures, partially failed, failed, stopping, stopped, waiting for approval or rejected. Running states appear in an information color, completed states in a success color, failures and errors in an error color, and states that need attention (e.g., stopped or waiting for approval) in a warning color.

A run rejected because of credits appears in a warning color rather than an error color, because it can proceed once the budget or your organization's credits allow it. See Troubleshooting Agent Team Runs Blocked by Credits in GTM One.