Stuck chat / Infinite loading screen

提交前确认 · Pre-submission checklist

• 我已搜索过现有 issue，确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
• 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.

问题类别 · Category

稳定性 / 崩溃 · Stability / Crash

涉及的 Agent 框架 · Agent framework

ZCode Agent（自研）

严重程度 · Severity

阻塞使用 · Blocking (无法使用核心功能 / core function unusable)

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

'm running into an issue where one of my chats is completely stuck on an infinite loading screen on the web browser. I can't access my history for it.

复现步骤 · Steps to reproduce

Open this link:https://chat.z.ai/c/317cc44c-c92f-4aa2-9e3a-261cde9be2a4

期望表现 · Expected behavior

Should show my chat

实际表现 · Actual behavior

Shows a loading screen forever

ZCode 版本 · ZCode version

I'm using newest web app version

设备 / 系统 / 浏览器 · Device / OS / Browser

Honor 200

截图 / 录屏 / 日志 · Screenshots / Recordings / Logs

Here are the details:
Account Email: cheungbrandan@gmail.com
Chat Title: Lifelong OS Rebuild Directive
User

ID:02dfe15a-2634-4e97-a2f6-b65090d0 1def

When it happened: About a 2 weeks ago (early July)

Device:Laptop and phone (Web Browser)

Note on length: This was a massive chat, around 750,000 tokens.

I've already tried the usual fixes (clearing cache, trying different networks, logging in on other devices), but this specific chat just keeps loading forever. All my other shorter chats work perfectly fine.

Since it's a 750k token chat, I'm guessing it might be a server-side timeout or a database lock on the backend when trying to fetch the session data.

Could you guys look into this and help me get it unstuck? If the Ul is permanently bugged because of the length, is there any way you could export the raw text or JSON of this session from the backend and email it to me? I really need the data from this chat.

Thanks so much for the help!

Start by reproducing the chat at the issue's URL in the web app and compare it with shorter chats, using the reported 750,000-token size and cross-device behavior as context. Done means the affected chat loads normally or its session data can be exported as requested.