agent context overflow loading three years of account notes into one meeting brief
Fixes the meeting prep agent failure agent context overflow loading three years of account notes into one meeting brief by applying the specific fix in the steps, proving it on one item first, then rerunning the full scope and reconciling the result. Use when this error blocks the work named in the title. Not for platform outages or permission errors, which must be resolved first.
TL;DR
Fix this in meeting prep agent by acting on the exact message first: summarise account notes by quarter into a compact running digest before brief building, load only the digest plus the last two quarters of raw notes, and keep the full note archive on file for lookup instead of in the brief context. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.
agent context overflow loading three years of account notes into one meeting briefUse this when
- The operation in meeting prep agent fails with this exact message: agent context overflow loading three years of account notes into one meeting brief.
- The same failure repeats on retry with unchanged inputs.
- A call, review or send is blocked until this item completes.
Not for this skill when
- The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
- The operation completes and you only disagree with its output. That is a quality review, not this failure.
Steps
- Reproduce the failure with the smallest scope that still shows it in meeting prep agent, and copy the full message plus the account, contact or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
- Apply the specific fix for this error: summarise account notes by quarter into a compact running digest before brief building, load only the digest plus the last two quarters of raw notes, and keep the full note archive on file for lookup instead of in the brief context. Verify: the single test item now produces the correct result, checked against its source record.
- Check the neighbouring items that share the same template, integration, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
- Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
- Rerun the original operation in meeting prep agent on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
- Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.
Why it happens
Three years of notes dwarf the meeting specific facts the brief needs, so loading everything overflows context before attendee and deal data are even added.
Variant phrasings
agent context overflow loading three years of account notes into one meeting brief
The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.
How to fix - agent context overflow loading three years of account notes into one meeting brief
The how-to phrasing for the same failure in meeting prep agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.
Troubleshooting this failure in meeting prep agent
The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.
Compatibility: meeting prep agent at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_qGpkQAZ4RMFdYUlIrMv0Xw