Threaded Comments: replies posted from the mobile app do not render in the task comment pane on web

English Forum Product Feedback
1

Hi Asana team :waving_hand:

First off — thanks for shipping Threaded Comments. It’s a feature our team had been waiting for, and the Inbox grouping is a real improvement for following multi-topic tasks.

We’ve run into what looks like a gap in the rollout, and since we were able to isolate it pretty precisely we wanted to share the details in case it’s useful to you.

Summary

Comments authored from the Asana mobile app are saved correctly on the server and appear in the Inbox (grouped under the new “Thread with …” view), but they do not render in the task’s comment pane on web. Comments authored from web render normally.

The practical impact is that teammates believe their message was never delivered, and the recipient never sees it unless they happen to open the Inbox item. No data is lost — the comments are all retrievable via the API — but the task itself becomes an unreliable record of the conversation.

Symptoms started on 4 August 2026, one day after Threaded Comments went live.

Steps to reproduce

  1. On web, open a task and post a comment.
  2. From the Asana mobile app, reply to that comment.
  3. Return to web, hard-refresh, and open the same task → the mobile reply is absent from the comment pane.
  4. Open the Inbox on web → the same reply is visible, grouped under “Thread with …”.
  5. GET /tasks/{task_gid}/stories → the reply is present, with target pointing at the correct task and source: "mobile".

Reproduced on two separate tasks, by two different users, on two different days.

Evidence

Workspace GID: 77217229939757

Case A — task 1217087466601394

Story GID Created (UTC) Author source Renders in task pane?
1217165703737061 2026-08-04T19:36:34Z User A web :white_check_mark: Yes
1215110364965095 2026-08-04T19:46:38Z User B mobile :cross_mark: No

Case B — task 1217165703737059

Story GID Created (UTC) Author source Renders in task pane?
1217173213896609 2026-08-04T22:59:58Z User B web :white_check_mark: Yes
1212848175200428 2026-08-04T23:22:27Z User A mobile :cross_mark: No

Across both tasks: 9 of 9 web-authored comments render; 0 of 2 mobile-authored comments render. The correlation with source is exact.

Possible lead: out-of-range story GIDs

This may or may not be related, but it stood out. The two non-rendering stories carry GIDs well below the allocation range in use that day — every other story created on 4 August sits in the 1217… range, while the two mobile ones are 1215110364965095 and 1212848175200428.

More specifically, 1212848175200428 falls inside the ID block occupied by existing tasks in the same project — 1212848175200425 and 1212848175200429 are both live tasks in that project. If the web client keys or de-duplicates its store by GID, a collision like that would plausibly cause the story to be dropped silently at render time, which matches the behaviour exactly.

Environment

  • Asana web on Chrome (Windows) + Asana mobile app
  • Free/Basic plan
  • Region: US

Happy to provide additional story GIDs, API payloads, or to test a fix on our workspace if that helps. Thanks again for the work on this feature.