Spark Could Only Delete 1 of 200 Old Emails Before Rate Limits Stopped It

Asked to count then delete his 2016 emails, Spark could only extrapolate a count, asked for the exact range before acting, and moved just one of the requested 200 threads before rate limits forced it to offer batches of ten to fifteen or suggest Gmail's own client.

This one went wrong. Read what happened so you don’t hit the same problem.

How it works

Try to count a year's email
Fail to enumerate
Confirm exact range and Trash-only
Delete 1 of 200
Hand back the rest

Why it’s worth knowing

The agent refused to guess, then proved it could not do bulk deletes at all.

Where it’s from

Summarized from a public post on techmitra.in. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be

2The prompt, with the steps

3The check when it’s done

Upgraded prompts are coming soon.

Try next

Life adminHe runs his dad's work orders and meeting scheduling out of his dad's inbox Life adminTriage my 2,000-email Outlook backlog and write native inbox rules Life adminMy Dot went through 15 years of marketing mail and unsubscribed me Life adminFind and pay my overdue NYC parking ticket$115

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.