# User Memory Save Bug

**URL:** <https://community.pickaxe.co/t/user-memory-save-bug/8518>\
**Category:** Bugs / Site Issues\
**Tags:** user-memory\
**Created:** [May 10, 2026, 4:58pm UTC](https://community.pickaxe.co/t/user-memory-save-bug/8518 "2026-05-10T16:58:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![enochleffingwell](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/enochleffingwell/32/1613_2.png) [@enochleffingwell](https://community.pickaxe.co/u/enochleffingwell)\
**Post date:** [May 10, 2026, 4:58pm UTC](https://community.pickaxe.co/t/user-memory-save-bug/8518/1 "2026-05-10T16:58:17Z")

</div>

My user’s are getting these strange messages when trying to use my pickaxes. Clearly it looks like on the backend it’s trying to save the user answers to their user memory but it’s failing.

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/2/2e206870b7ff085b5cda6e45eefad0a5c88e05e4.png)

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/c/c6c5ab6cacf94fd3e4f9db8abaceb8852934dd54.png)

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/f/fa5e3fcde8a75ef7905cebdc80487fdfa0d94478.jpeg)

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/8/87818b3315d028ba4ced4ad0f450b4fc0b5e78a9.jpeg)

My user sent me a message saying “I looks like it’s going to respond constantly but it never responds”

So it looks like there was 3 errors that my users are facing today.

I’d lie to get some help on these matters. Thank you for taking a look!

@stephenasuncion @lindsay_support

---

<div class="post-metadata">

**Author:** ![danny\_support](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/danny_support/32/3492_2.png) [@danny\_support](https://community.pickaxe.co/u/danny_support)\
**Post date:** [May 11, 2026, 8:56pm UTC](https://community.pickaxe.co/t/user-memory-save-bug/8518/2 "2026-05-11T20:56:14Z")

</div>

> [@enochleffingwell](#):
>
> My user’s are getting these strange messages when trying to use my pickaxes. Clearly it looks like on the backend it’s trying to save the user answers to their user memory but it’s failing.
> 
> ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/2/2e206870b7ff085b5cda6e45eefad0a5c88e05e4.png)
> 
> ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/c/c6c5ab6cacf94fd3e4f9db8abaceb8852934dd54.png)
> 
> ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/f/fa5e3fcde8a75ef7905cebdc80487fdfa0d94478.jpeg)
> 
> ![image](https://canada1.discourse-cdn.com/flex004/uploads/pickaxeproject/original/2X/8/87818b3315d028ba4ced4ad0f450b4fc0b5e78a9.jpeg)
> 
> My user sent me a message saying “I looks like it’s going to respond constantly but it never responds”
> 
> So it looks like there was 3 errors that my users are facing today.
> 
> I’d lie to get some help on these matters. Thank you for taking a look!
> 
> @stephenasuncion @lindsay_support

Hi @enochleffingwell ,

Thank you for reaching out and for sharing these details.

We have reported this to our engineering team, and they are currently looking into it. I’ll follow up here as soon as we have more information to share.

---

<div class="post-metadata">

**Author:** ![danny\_support](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/danny_support/32/3492_2.png) [@danny\_support](https://community.pickaxe.co/u/danny_support)\
**Post date:** [May 15, 2026, 8:01am UTC](https://community.pickaxe.co/t/user-memory-save-bug/8518/3 "2026-05-15T08:01:14Z")

</div>

Hi @enochleffingwell ,

Thank you for your patience while we looked into this.

**Regarding your first two screenshots:**

We investigated the conversation and found that the visible \<one\_moment\> / dory/save\_memory text was not an actual platform command being exposed. It was a hallucinated internal-style string generated by the AI.

What likely caused it is the prompt setup for that tool. Multiple instructions repeatedly told the AI to save each answer into user memory, included a long list of example memory labels, and also said: “If the platform provides a specific memory mechanism, use it for each answer as soon as it is given.” Because the prompt strongly pushed the model to save memories directly during the conversation, the model appears to have invented its own pseudo-command format and printed it into the response.

We also checked whether this was a real backend memory tool leaking through, and we did not find evidence of that. The text was stored as normal assistant message text, not as an actual tool/action call. So the issue is best understood as an AI hallucination triggered by the prompt instructions.

Backend logs also show that this conversation did create new user memory entries, so this does not appear to be an issue with memories failing to record. In this case, the user memory system was still working, while the AI separately hallucinated the visible dory/save\_memory text in the chat.

The best next step is to simplify the memory-related instructions in the role prompt and keep them light. The stronger guidance should live in each configured user memory’s own prompt field, with clear and unambiguous instructions about what to collect and when to collect it.

**Regarding your third screenshot about a client-side browser error:**

That message usually appears when the page loads, but then the browser hits a frontend JavaScript exception and stops rendering properly. In your screenshot, it looks like the page is being opened inside Messenger’s built-in browser, which can sometimes behave differently from the normal Chrome or Safari app. Because of that, it can mishandle newer JavaScript features, local/session storage, redirects or login flows, popup logic, or cached scripts.

Please try the following steps:

- Open the same link directly in your normal browser instead of inside Messenger.
- Try an incognito/private window to rule out cached data or stored session issues.
- Clear your browser cache and cookies, then reload the page.
- If possible, test from a different browser or device to help isolate whether it is browser-specific.

If the error appears again, please open the browser console and send us a screenshot of any messages shown there. That will help us narrow down the exact cause.

**Regarding your last screenshot showing the Failed to fetch message** , that error usually appears when the browser is unable to complete the network request. In your screenshot, there is a “No internet connection” message visible at the top, so the most likely cause is that the connection dropped while the conversation was in progress.

Please let us know if you continue to see any of these issues, and we’ll be happy to investigate further.
