Troubleshooting Agent Team Batch Runs in GTM One

Learn how to resolve common issues with agent team batch runs.

Overview

A batch run runs an agent team across many inputs at once, such as the rows of an audience or a CSV file. Each run in the batch has its own status, and the batch run results show the output of each step in its own column. Use this article when a batch run is rejected or stopped, when you cannot export results, or when an output column does not show what you expect.

Credit budgets are available when your organization has them turned on. Without them, a run can still be rejected when your organization runs out of credits.

A batch run was rejected for credits

A run can be rejected when the agent team reaches its credit budget or when your organization runs out of credits. The run status tells you which of the two happened. A credit rejection is shown as an attention state rather than an error, because it clears once the budget is increased or credits are available again. If the whole batch was rejected, the batch run results show a banner and an empty state in place of results.

1. Open the agent team and go to its batch runs.
2. Check the run status to see whether the agent team's budget was exceeded or your organization's credits are exhausted.
3. If the budget was exceeded, increase the agent team's credit budget.
4. If your organization's credits are exhausted, buy more credits or ask your admin to add credits.
5. Open the actions menu for the rejected run and choose to reinitiate it. A confirmation shows the ID of the queued run, with an option to view it.

The option to reinitiate can ask you to increase the budget or buy credits first, so complete step three or step four before you reinitiate.

A batch run stopped

A run that is being stopped shows a stopping status, and then a stopped status once it has ended. The batch run results show a banner when the batch stopped.

1. Open the agent team's batch runs and filter by run status to find the stopped runs.
2. Review which runs completed and which did not.
3. Run the agent team again for the inputs you still need to process.

The export option is unavailable

The export option in the batch run results can be unavailable, for example when nothing is selected, when the batch failed, or while results are still pending.

1. Hover over the export option to read the tooltip that explains why it is unavailable.
2. Resolve that condition (e.g., select the runs you want to export, or wait for pending results to finish), then export again.

If the export fails after you start it, a message confirms the error. Try the export again.

An output column is empty or shows unexpected content

Each step of the agent team has its own output column, and the column header tells you where the step sits in the agent team:

• "Output: Step 2" is a top-level step.
• "Output: Step 1.2" is the second step inside a loop at step one.
• "Output: Step 2/Condition 1/Step 1" is the first step on the first condition of a branch at step two.
• "Output: Step 2 Conditional routing" is the branch step itself, and it shows the path that was taken for that row.

When an output cell looks empty or incomplete, check the following:

1. For a step inside a branch, check the conditional routing column for that row. A step on a path that was not taken does not run, so it has no output for that row.
2. For a step inside a loop, remember that the column shows only the output of the first loop item. Open the individual run to see the output of every iteration.
3. Open the individual run to review each step. A step that produced nothing shows "No output available", and a branch step shows either the condition it matched (e.g., "Condition 1: ...") or "Default path taken - no conditions met".

For a run that used a CSV file, the inputs show a "CSV file" entry with the file name, so you can confirm which file the run used.