zai-org / zai-org/feedback

[Bug] Web UI throws Oops, something went wrong. Please refresh the page or try again later.

Open
#468 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: Bug
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

提交前确认 · Pre-submission checklist
  • 我已搜索过现有 issue,确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
  • 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

严重程度 · Severity

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

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

When I ask the model to continue with the task I get Oops, something went wrong. Please refresh the page or try again later.. Unable to continue the chat after that. All my context and work are stuck in that specific chat.

复现步骤 · Steps to reproduce

Not replicable in new chats.
When I put any prompt I get
Oops, something went wrong. Please refresh the page or try again later.

期望表现 · Expected behavior

It should start working on the prompt.

实际表现 · Actual behavior

Throws an error

ZCode 版本 · ZCode version

NA

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

PC/Windows 11/Chrome

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

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure in the affected existing chat on PC/Windows 11/Chrome, then compare it with a new chat where the problem does not occur. No source files or tests are identified; the issue is complete when prompts can continue in the affected chat without the error.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.