lm-sys / lm-sys/FastChat

## Chat History Recovery Request: Single Session Fails to Load After Message Error

Open
#3,758 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
39.5k
Forks
4.8k
PR merge metrics
No merged PRs in 30d

Description

### 🐛 Problem Description

A single, crucial chat history session is currently failing to load or open within my LM Arena account. This conversation contains vital, long-form strategic information (approximately 2.5 hours of work) that I urgently need to recover.

### 📍 Steps Leading to Failure

1. I was using the LM Arena web interface on an **Android mobile browser**.
2. The conversation was very long, lasting approximately **2.5 hours**.
3. The issue occurred when the **last message I sent highlighted red**, indicating it failed to send.
4. After clicking the **"Retry"** button, the entire chat session immediately became inaccessible.
5. All other chat histories in my account load and open correctly.

### 🛑 Actual Outcome

When I click on the history entry for the corrupted session, the page fails to load the content. It either gets stuck loading or displays a blank/new chat window instead of the history. The content is inaccessible.

### 💡 Request for Assistance (Urgent Data Retrieval)

Since all client-side troubleshooting (clearing browser cache/site data, logging in/out) has failed, I strongly suspect this is a **server-side data corruption or synchronization error** caused by the failed message/retry attempt.

**I kindly request that the development team manually retrieve and export the text content of this specific corrupted chat session.**

**I am ready to provide my account login email/username privately upon request (e.g., via email or Discord DM) so the team can quickly locate the data.**

Contributor guide

No contributing guide indexed for this repository

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

The issue identifies an Android browser failure after retrying a red failed message, but names no repository file, test, or entry point. Start by reproducing the affected session's loading failure and tracing the history-loading path; done would mean the specific chat opens and its text is recoverable.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, python
Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.