# Grok Bot update\_state memory writes fail fleet-wide: brain docs snapshot was cut short before completing **URL:** \ **Category:** Bug Reports\ **Tags:** grok-bot\ **Created:** [September 16, 2026, 3:07pm UTC](https://forum.cursor.com/t/grok-bot-update-state-memory-writes-fail-fleet-wide-brain-docs-snapshot-was-cut-short-before-completing/171895 "2026-09-16T15:07:36Z")\ **Posts on this page:** 1\ **Showing post:** 18
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [September 26, 2026, 9:52am UTC](https://forum.cursor.com/t/grok-bot-update-state-memory-writes-fail-fleet-wide-brain-docs-snapshot-was-cut-short-before-completing/171895/18 "2026-09-26T09:52:11Z")
Hey @Matt_Devaney, @Amogh_Tyagi, thanks for the details. There’s an important distinction here. The original issue in this thread (`brain docs snapshot was cut short` during memory-write) has been fixed, and the OP confirmed that above. What you’re describing, a crash of the `create` routine with `Not saved: the routine could not be saved on the server this turn (create failed)`, is a separate issue and not related to memory. I can see that memory-write, rules, chat, and shell work for both of you, and only routine creation fails. To speed up debugging, a couple questions: - The Request ID for a failed create attempt, if Privacy Mode isn’t enabled: in the bot chat, top-right menu \> Copy Request ID. - @Matt_Devaney, on the same bot, does create fail for any routine, or only for a specific payload? Do update, pause, delete for existing routines work? So this routine issue doesn’t get lost in a thread about an already-fixed memory bug, please continue in a separate topic. Please create a new thread for your issue. --- _[View the full topic](https://forum.cursor.com/t/grok-bot-update-state-memory-writes-fail-fleet-wide-brain-docs-snapshot-was-cut-short-before-completing/171895)._