Troubleshooting agent team steps that did not finish in GTM One

Learn why an agent team step can end as failed even though it ran, and how to get it to finish.

Overview

An agent team step works in rounds: it asks the AI to use its tools, reads the results and decides what to do next. After a step finishes, GTM One checks the result against what the step was asked to do. A step is marked failed, and the run fails, when the check shows the work was not done. This protects you from a run that reports a success it did not achieve, such as a message "sent" with no sending tool, or a report built on data that never loaded.

On the failed run's What went wrong card these show as "Step didn't finish" or "Missing data". See Troubleshooting the "What went wrong" card on a failed agent team run in GTM One.

Before you start

• Permission to edit the team. Every fix below edits a step. If the builder's controls are turned off, ask your ZoomInfo admin.
• Real effects. A step that did not finish may still have done part of its work: records created, messages sent. Check the destination before you run again, so the second run does not repeat it.
• Credits. A run that fails, stops or is rejected still uses AI credits for the work it performed. A run that never started uses none.

Find out why the step did not finish

1. Open the failed run and click the failed step. See How to view agent team runs and results in GTM One.
2. Read the step's output and the What went wrong card, then find the matching case below.
3. Make the fix in the builder. See How to edit an agent team's steps before running it in GTM One.
4. Start a new run. See How to run an agent team manually in GTM One.

The step reached its limit of tool-call rounds

A step may use up to 50 rounds of tool calls. A step that is still working at the limit is stopped and asked to report what it finished. The step's output then reads:

• "This step reached its limit of N tool-call rounds before it finished." followed by Completed: and Not completed: lists. The completed part is kept and passed to later steps.
• "This step reached its limit of N tool-call rounds, and whether it finished could not be confirmed. Its last result follows." The report could not be made, so the output is the step's last result.
• "This step's work spans N attempts: each earlier attempt reached its tool-call round limit before it finished, and the next one continued it." The step was retried, and each attempt's results follow in order.

To fix it:

1. Split the work into smaller steps, or use a For Each step so each item is its own pass.
2. Narrow the instructions to one task, with the exact tool and values to use.
3. Remove tools the step does not need, so it does not wander between them.

The step was rejected five times in a row

After each step, a reviewer pass can send it back to try again. A step that is sent back five times in a row without finishing (the first attempt and four corrections) is abandoned, and the run moves on with the step marked failed. The run's raw error, under Show technical detail, reads "was rejected by its supervisor" and the number of times "in a row without ever completing, so the run stopped retrying it and moved on. The step is recorded as failed."

To fix it, make the step's instructions specific about what a finished result is, and check the step has the tools and access it needs. A step that is asked for something it cannot do will keep being sent back.

The step claimed work no tool did

A step is failed when every tool call it made failed, or it made none, and its output still says it sent, created or updated something. The card reads "Step didn't finish". Check that the step has the tool it needs (for example the send or create action) and that the app is connected, then run again. A step that honestly reports it could not get data is not failed by this check.

The step ran without data it needed

When a read the step needed failed and the run went on to deliver a result built without it, the run fails and the card reads "This step ran without data it needed." Label: "Missing data". Fix the connection or the source that failed (look for a not-connected or permission message on an earlier step) and run again. A read that worked but found nothing, such as no matching contact, is not a failure.

The step acted on a different target than asked

When the step could not find the person, channel or record it was asked to reach, and then acted on a different one, the run is failed even though the action went through. The message begins with the tool and says it was asked to reach a target, that no lookup confirmed one, and that the call that followed acted on something else. The action did take effect, against a target the run never confirmed. Check where it landed and correct it by hand, then fix the step so the lookup succeeds, for example by giving the full email address.

Update Audience has no Audience to update

A run is refused before any step starts when an Update Audience step names no Audience. The message reads "Update Audience has no audience to update:" followed by the step names, then "Select an existing audience, or the earlier Create Audience step whose audience it should update." Open the step, select an existing Audience or the earlier Create Audience step, and save. If the earlier Create Audience step did not produce exactly one Audience, the Update Audience step fails instead of searching for a similar Audience.

A step is told to call a tool nobody on the team has

A run is refused before it starts when a step's instructions name a tool that no step in the team can call. The message names the step and the tool, and where the instructions first name it. Open the step and remove every mention of the tool, or name a tool the step already has, then save and run again. If the step genuinely needs the tool, contact your ZoomInfo support contact.

If you see an error

• "Update Audience has no audience to update:" An Update Audience step has no Audience chosen. Select an Audience or an earlier Create Audience step.
• "This step reached its limit of N tool-call rounds before it finished." The step ran out of rounds. Split the step or narrow its instructions.

Resources

• Troubleshooting the "What went wrong" card on a failed agent team run in GTM One
• Overview of agent team steps