chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix: prevent task lane from showing previous session's data on switch

Browse Source 
Root cause: race condition between setActiveChatId and the persist
effect. When switching from session A to B, setActiveChatId(B) triggers
the persist effect which writes {chatId: B, questions: [A's data]} to
sessionStorage BEFORE the async selectChat clears the task lane. The
sessionStorage fallback then finds chatId === B and restores A's stale
task lane data.

Fix: clear task lane state synchronously in selectChat before the await.
Server-side pending_task_lane restores it if the new session has data.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
chihlasm
2026-04-03 05:23:55 +00:00
parent 813b598101
commit b03f84aecf
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
frontend/src/hooks/useAssistantSession.ts
View File

@@ -169,7 +169,12 @@ export function useAssistantSession() {
const selectChat = useCallback(async (chatId: string) => { const selectChat = useCallback(async (chatId: string) => {
currentChatRef.current = chatId currentChatRef.current = chatId
setActiveChatId(chatId) setActiveChatId(chatId)
// Don't clear task lane yet — wait for server response to decide // Clear task lane immediately to prevent the persist effect from
// tagging the old session's data with the new chatId (race condition).
// Server-side pending_task_lane will restore it below if it exists.
setActiveQuestions([])
setActiveActions([])
setShowTaskLane(false)
try { try {
const detail = await aiSessionsApi.getSession(chatId) const detail = await aiSessionsApi.getSession(chatId)
if (currentChatRef.current !== chatId) return if (currentChatRef.current !== chatId) return