[Due for payment 2025-10-21] [Due for payment 2025-10-15] Expense - "marked as paid" message from OD cannot be copied, thread header loads infinitely

[mitarachim]

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: 9.2.19-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #70694
Email or phone of affected tester (no customers): jsdiojndoijosidnjo@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Click Submit and Approve.
5. Log in to staging.expensify.com with the same account.
6. Open the same report.
7. Click Reimburse > I'll mark it manually.
8. Open the expense report on ND.
9. Right click on "marked as paid" system message > Copy to clipboard.
10. Paste the content.
11. Right click on "marked as paid" system message > Reply in thread.

Expected Result:

In Step 10, the system message is copied.
In Step 11, the system message thread will load without issue.

Actual Result:

In Step 10, the system message is not copied.
In Step 11, the system message thread header shows skeleton loader.

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

Bug6957147_1758929593325.Screen_Recording_2025-09-27_at_07.21.42.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot]

Triggered auto assignment to @OfstadC (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]

Triggered auto assignment to @Julesssss (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.