[$250] Thread - Hidden in LHN and loading header when thread reply on system message

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.75-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76209
Email or phone of affected tester (no customers): applausetester+dp301n@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac / Safari
App Component: Left Hand Navigation (LHN)

Action Performed:

1. Go to workspace chat (WS chat).
2. Create an expense.
3. Open the expense.
4. Click “Report”.
5. Remove the expense from report.
6. Go to your self DM chat.
7. Open the “unreported expense” message.
8. Right-click on the system message that indicates the report was moved.
9. Submit a message in the thread.

Expected Result:

The reply message appears immediately with the correct header.
The thread is visible in the Left-Hand Navigation (LHN) as expected.

Actual Result:

After submitting the message, the header stays in “loading” mode.
The thread is hidden in the LHN.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021999592012393993056
• Upwork Job ID: 1999592012393993056
• Last Price Increase: 2026-03-02

Issue Owner

Current Issue Owner: @akinwale

[melvin-bot]

Triggered auto assignment to @isabelastisser (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021999592012393993056

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale (External)

[marufsharifi]

This seems to be a BE issue
When adding a comment to a child thread, the backend sends an Onyx merge that first sets the parent report action to null, then merges back only child-thread metadata fields.
This permanently removes required fields (actionName, message, originalMessage) from the parent action in Onyx, causing the report title to disappear until OpenReport rehydrates the action.

[melvin-bot]

@akinwale Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!