When update_state memory fails with brain docs snapshot cut short

Asking a Bot to save a durable fact with update_state (memory target) can fail with:

brain docs snapshot was cut short before completing

Staff (deanrie, Sep 16, 2026) on forum 171895 call this a known tracked issue. It is not caused by one oversized chat. Settings updates and direct edits under the Bot’s memory files can still work while the memory tool path fails. Host stamps such as brain_docs_compensation_failed / brain_docs_channel_config_corrupt may appear on the box.

Routine create can fail with Not saved while memory still works (When Grok Bot routine create returns Not saved). If memory writes succeed and only routine create fails, follow that how-to.

Confirm the error class

1. Ask the Bot to write a short memory fact with update_state target memory.
2. Note the exact error string. Brain-docs wording is this path.
3. Ask the Bot to change a harmless settings field (for example a note in profile settings). If settings succeed while memory fails, you are on the brain-docs miss.
4. Do not Update or Reset Agent Computer as the first fix — staff said Reset does not clear this.

Persist facts with file append while the tool is down

Staff’s workaround: append important facts to memory files on the Agent Computer instead of relying on the failing tool.

1. Ask the Bot to open its memory folder on the shared computer.
2. Append a self-contained sentence to memory/profile.md for lasting identity facts, or to memory/log/YYYY-MM.md for dated history (use the current year-month).
3. Keep each fact one clear sentence the next Bot turn can read without the tool.
4. Retry update_state memory later when staff closes the incident; keep using file append for anything you cannot afford to lose.

Example ask:

Memory update_state is failing with brain docs snapshot cut short. Append this fact to memory/profile.md as one sentence, and confirm the file write succeeded: …

What not to do

• Update Computer / Reset Computer / create a duplicate Bot solely to clear brain-docs errors.
• Stuff long essays into a single append — prefer short facts you would have stored as profile or log entries.
• Assume every Bot on the account is healthy because one still accepts memory writes — the failure can be fleet-wide or Bot-specific; test the Bot you care about.

Watch 171895 for staff confirmation that the tool path is fixed before you drop the file-append habit.

Pitfalls

• Treating brain-docs memory failure and routine Not saved as the same bug — different strings and different workarounds.
• Resetting the computer because memory writes failed — staff guidance says that does not fix this path.
• Leaving load-bearing facts only in chat while the tool is down — append to memory/profile.md or the monthly log file.