First, stop retrying the same send and find out which limit you hit. A Gmail sending-limit message, an application’s empty budget and an API request-rate error can require different responses. Changing tools or connecting another account does not explain the original failure.

Save the exact error and note where it appeared: Gmail, a campaign screen, or an application log. Also record the sending account, the last successful send and whether ordinary mail is affected. Those details are more useful than “Gmail is broken.”

Observable symptom Who owns the next check? First action
Gmail refuses an ordinary message with the limit warning Sender, or Workspace administrator Stop sending and check provider/account limits
ColdMerge names an exhausted budget term Sender or Organization Admin Read that term in Send budget
An application log names a request-rate error Application operator Check the exact API reason and backoff handling
The error names a domain policy or disabled service Workspace administrator Check the policy; changing an app cap will not fix it

Do not test repeatedly by sending another campaign. Use the error and existing send history to choose a branch first.

If Gmail shows the sending-limit message

Google’s consumer help describes this message when daily sending or per-message recipient limits are exceeded. It says sending generally becomes available again within 1 to 24 hours. Do not read that as a guaranteed recovery time for every restriction. Google’s limit-error help.

For a work or school account, check Google Workspace’s sending limits. Those limits use a rolling 24-hour window. Google says an account that exceeds a sending limit can be unable to send new messages for up to 24 hours. Ask your administrator to check the account’s status; changing an application’s cap does not clear a Google restriction.

Check what you already sent from that account, including mail outside the campaign. A tool’s count may not tell you everything Google has seen. Also check whether you attempted a single message with a large recipient list.

Wait rather than repeatedly submitting the same batch. When sending becomes available, reduce the queued work and review the cause. If ordinary mail remains blocked or a different account warning appears, follow the account-specific guidance instead of assuming another daily wait will fix it.

If the campaign says the app budget is empty

In ColdMerge, the mailbox’s current budget is the lowest applicable limit. The reason can be connection age, recent sending volume, your configured cap, a product ceiling or a trial allowance.

For example, a paid organization may have a configured mailbox cap of 25 and already have 25 counted sends in the rolling window. That is an exhausted configured budget. It is not evidence that Google has suspended the mailbox.

If the configured cap is genuinely too low for your intended work, review it. If rolling usage is binding, wait for capacity to return. If the whole-trial allowance is exhausted, a midnight reset will not refill it. The budget reference separates those cases.

If the error comes from the API

An API error needs its code and reason, not just a screenshot of “limit exceeded.” Google’s dailyLimitExceeded reason refers to a project’s API quota. Request-rate errors call for application backoff; an administrator’s domain policy can require administrator action. These are different from a user’s mailbox sending quota. Google’s API error guide.

An HTTP 429 alone does not identify the cause: Google also uses it for bandwidth and concurrent-request limits. The application operator should inspect the full reason before choosing a response.

If you are the sender rather than the application operator, provide the error to support. Include the time and account, but remove tokens, authorization headers and recipient data. Do not change a mailbox’s daily cap to solve a shared project quota.

A short diagnosis record

Copy this record into your own incident notes:

Time and timezone: 10:15, Africa/Lagos
Account type: consumer Gmail
Where it appeared: campaign budget panel
Exact reason: configured cap exhausted
Last accepted send: 10:12
Usage shown: 25 counted / cap 25
Ordinary Gmail affected: not established
Accepted / unsent recipients: check campaign records before retrying
Next check: Settings > Accounts > Send budget

This is a fictional app-budget incident, not a provider error. Replace each value with what you observed. For a support request, use the account identifier support needs and remove private recipient data or authentication secrets.

Then choose the response that matches that record. An empty app budget leads to a budget review. A provider refusal leads to provider guidance. An admin block leads to the administrator. Keep the original queue intact until you know what was accepted, so retries do not create duplicates.

Once the immediate problem is resolved, use the mailbox budget reference to plan the next batch. The goal is a campaign you can explain and monitor, not a way around a refusal.