## TL;DR
Pause the workflow for draft a follow-up email from a call summary until the email service rate limit window resets, then resume with backoff and batched requests, caching the call and attendee lookups instead of refetching them per item, because the run burned its API budget mid task and every call after the limit failed identically. Start with the call summary and the follow-up draft it produced, and the agent run log for the step where it stopped, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

```text
email API rate limit hit mid-call summarization workflow when agent tried to draft a follow-up email from a call summary error failed quota
```

## Use this when
- You see this exact message or symptom: email API rate limit hit mid-call summarization workflow when agent tried to draft a follow-up email from a call summary error failed quota
- One run, record, call, or object is affected and you can name it
- A retry without changing anything reproduces the same result

## Not for this skill when
- The system fails with a different message and none of the signals here appear
- Nothing has failed yet and you are doing first time setup or general planning
- Every service from this vendor is down for all users, which is a vendor outage to wait out first

## Steps
1. Reproduce the failure once using the call summary and the follow-up draft it produced, and the agent run log for the step where it stopped, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the call summary and the follow-up draft it produced. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Pause the workflow for draft a follow-up email from a call summary until the email service rate limit window resets, then resume with backoff and batched requests, caching the call and attendee lookups instead of refetching them per item, because the run burned its API budget mid task and every call after the limit failed identically. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the draft covers the agreed next steps, names the right attendees, and matches the seniority of the customer audience
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

## Variant phrasings
### email API rate limit hit mid-call summarization workflow when agent tried to draft a follow-up email from a call summary error failed quota
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.
### Tool-first phrasing of this failure
The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
### Why does this keep happening after a retry
The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: email service exports and API at current versions, plus the CRM or sharing destination the task names; the steps assume the run can be resumed per call rather than only as a whole batch.

## Why it happens
Call summarization fans out into many small API reads per call: transcript pages, attendees, the destination record, then the write. A run sized for a few calls exhausts a per minute or per hour budget partway through a batch, and retrying inside the window only spends the recovery time.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iykfs8N5v8On9WaC_UwJqA