You hit a daily sending cap mid-batch: some rows went out, some did not. The fix is not a tool that promises to exceed the limit — no add-on can. The fix is splitting the batch across days so already-sent rows can never be emailed twice.
Copy the sheet. Resolve the exact pending payload for every row. Already-SENT rows stay blocked by the 30-day protected-message fingerprint. Approve the unchanged preview once, then send only the remaining rows the next day.
A cap or error stopped the send partway; you need to finish without duplicates.
Planned sends split across days because the list is larger than the daily quota.
Decisions, invoices, notifications — rows where a second send is embarrassing.
A timed trigger failed and you need to resume with a clear audit trail.
Gmail enforces daily sending limits at the account level. No add-on, script, or workaround sends more than your account allows in a day. Anyone promising otherwise is selling something Google will block. The safe strategy is planned multi-day batches with duplicate protection — not limit evasion.
You know exactly which rows sent and which did not, because every row carries a SENT / SEND_UNCERTAIN status instead of a vague "done".
A 30-day ledger blocks replays even if rows move, get copied, or have their status cells cleared — the classic cause of accidental double sends.
No. It lets you finish a large send across multiple days without emailing anyone twice. The limit still applies per day.
Do not retry it blindly. Check the recipient inbox first, then mark it verified sent or reset it. Ambiguous sends stay blocked until a human decides.
Prove the recovery path on a copied sheet with test inboxes before you trust it with a real half-sent batch. If Preflight, the exact preview, and the one-time approval all behave, that is the right moment to leave an honest Marketplace review.