Total workspace count not updated when a workspace is created asynchronously (e.g., via @-mention of an AI user)
#3276
-
Previous Value Current Value Workspace count for AI user not updated after workspace is created via @-mention
Workspace count not updated after workspace is created via @-mention
-
Previous Value Current Value Workspace count not updated after workspace is created via @-mention
Total workspace count not updated when a workspace is created asynchronously (e.g., via @-mention of an AI user)
-
Name Previous Value Current Value Priority
Normal
Minor
| Type |
Bug
|
| Priority |
Minor
|
| Assignee | |
| Affected Versions |
17.2.1
|
| Labels |
No labels
|
Issue Votes (0)
Summary
The total workspace count shown in the UI keeps displaying a stale value when a new workspace is created asynchronously — for example, when an AI user is @-mentioned in a comment and the agent subsequently creates a workspace. The count only corrects itself after a full page refresh or after an unrelated comment is added or deleted. Although this report uses the AI @-mention flow as the trigger, the affected value is the total workspace count, so the problem is not limited to AI-user workspaces.
What currently happens (Actual behavior)
What I want to happen (Expected behavior)
Steps to reproduce
Observed: the count is unchanged, even though a new workspace now exists.
Root cause analysis (suspected)
Three factors combine to produce the stale value:
Suggested fix
Preferred:
Alternative (if real-time updates are out of scope):
Motivation / Impact
Workaround
Refresh the page (or add/remove a comment) to force a server-side re-render of the fragment; the count will then be correct.
Acceptance criteria