fix(KB-613): resolve status update race condition and fix stuck timeout units
- Add timestamp comparison logic in handleUpdated to prevent stale websocket data from overwriting newer task state - Rename stuck timeout setting from minutes to milliseconds for finer control - Add comprehensive tests for status update race condition scenarios - Add changeset for status update race condition fix
This commit is contained in:
5
.changeset/fix-status-updates.md
Normal file
5
.changeset/fix-status-updates.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
"@gsxdsm/fusion": patch
|
||||
---
|
||||
|
||||
Fix dashboard status updates not showing until refresh (KB-613). The `handleUpdated` function in `useTasks.ts` now correctly uses `updatedAt` for general freshness comparison instead of relying solely on `columnMovedAt`, which was causing status updates to be incorrectly rejected as stale after column moves.
|
||||
Reference in New Issue
Block a user