Troubleshooting Audience Request Limits and Busy Errors in GTM One

Learn how to recover when GTM One tells you it has received too many audience requests, is busy, or is still working on a change.

Overview

GTM One protects audiences from floods of requests in two ways. A per-user limit caps how many requests one person (or one connected tool acting for them) can send in a minute. A capacity limit caps how many audience searches can run at the same moment. When either is reached, the request is refused for a short time and nothing is changed. Waiting a moment and trying again is the fix.

The per-user limit applies when your organization has it turned on. The capacity limit applies only when it has been switched on for the service during a heavy period. These messages appear only when a limit that is on has been reached, so not seeing them does not mean a limit is off.

You have sent too many requests

Opening the Audiences page, opening one audience, creating an audience and looking up which audiences a record belongs to each have their own allowance, and all requests count toward an overall allowance as well.

1. Stop the action that repeats, for example reloading the Audiences page or running many creations in a row.
2. Wait about a minute. The allowance refills as time passes, and the response states how many seconds to wait.
3. Try the action again.
4. If you run an automation or a connected tool that works on audiences, space its requests out.
5. If you keep reaching the limit during normal use, send the exact message and the time to your ZoomInfo admin or account team.

The audiences service is busy

When many audience searches run at once, new ones are refused straight away instead of waiting in line.

1. Wait a few seconds. The response asks you to retry shortly.
2. Reload the Audiences page or reopen the audience.
3. If the message continues for several minutes, send the exact message and the time to your ZoomInfo admin or account team.

A change is still in progress

Changes to a few rows are saved while you wait, for up to about 10 seconds. A change that takes longer keeps running in the background, and GTM One reports that it is still in progress.

1. Do not repeat the change straight away.
2. Wait a minute, then reopen the audience and check whether the rows and the records count have updated.
3. Repeat only the part that is missing. A record that is already in the audience is refused if you add it again (see Troubleshooting Audience Row and Column Changes in GTM One).

If you see an error

• "You have exceeded your API request rate limit. Please decrease the frequency of your requests." You sent more requests in a minute than your allowance. Wait a minute and try again.
• "Audience search is at capacity" followed by a number and "concurrent searches per instance). Retry shortly." Too many audience searches were running at once. Wait a few seconds and try again.
• "Job" followed by an id and "is still in progress after the maximum wait time". The change did not finish within the wait. Wait a minute, then check the audience before trying again.
• "Job not found for the given Id" followed by an id. The background job is no longer on record. Check the audience instead of waiting for the job.

Resources

• Troubleshooting Audiences in GTM One