Update to #99816

https://thebrain.zendesk.com/agent/tickets/99816

Hello Neil,

Thank you for the follow up.

Starting a new conversation with a carried over summary is the best practical workaround for now, especially with very long Cerebro threads. I understand it is not ideal, but very long AI conversations can become heavy and less reliable over time.

I’m still checking this with the team, and I want to clarify one detail so we can investigate the original stuck conversation properly.

In the affected conversation, are you still able to type and send a new message, but Cerebro simply never responds? Or are you unable to type into the message box at all?

If you are able to send a message, could you please do this:

• Open the affected Cerebro conversation
• Send a new message in that same conversation
• Wait at least 120 seconds
• Then send us the Output.log right afterward

Also, when you mentioned a “refresh request,” could you clarify what action you mean there? For example, are you clicking a retry or refresh button, resending the prompt, or doing something else?

Lastly, roughly how long is the affected conversation? Have you been using one continuous Cerebro conversation for most of this project, or have you already been starting new conversations along the way?

Best regards,

John