Conversation history stuck on old messages across multiple chats
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Several chats keep displaying older messages instead of the latest conversation. Fully closing and reopening the app does not fix it.
In SCOLAFLOW V.2, the visible history stops at an old desktop login-layout discussion, although substantial work and newer messages followed.
Read-only diagnostics found this repeated error:
thread history projection for 01a039ab-af20-77d0-872f-800d2cd0d56f
expected ordinal 8608, got 8607
The original transcript still exists and is being updated. However, the history index is stuck at byte offset 391604723, while the transcript is approximately 3.46 GB.
- Platform: Windows
- Date observed: 7 September 2026
- Restarting the app: no improvement
- Multiple chats affected; the error above was confirmed for SCOLAFLOW V.2
- No chat data or databases were modified during diagnosis
Please provide a safe way to repair or rebuild the conversation-history index without losing the original transcripts or recent messages.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or entry points are identified in the issue. Start by locating the conversation-history projection and index-rebuild code, then reproduce the ordinal mismatch using the reported diagnostics; done means a safe repair or rebuild preserves the original transcripts and newer messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100