[Due for payment 2025-06-11] [Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM

[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: 9.1.51-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check, new feature
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+jsidosjdno@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Log in with Expensifail account.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two expenses.
4. Click + > Create report.
5. Click on the report preview with expenses.
6. Select two expenses via checkbox.
7. Click More > Move expenses.
8. Select the new empty report from Step 4.
9. Click More > Delete.
10. Delete the report.
11. Go to self DM.
12. Click on one of the expenses.
13. Right click on "moved this expense to" message > Reply in thread.

Expected Result:

The system message for moving expense will be complete.

Actual Result:

The system message for moving expense is incomplete. It shows "moved this expense to".
When the message is opened in thread, it shows "moved this expense to Inaccessible Report".

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

Issue Owner

Current Issue Owner: @NicMendonca

[melvin-bot]

Triggered auto assignment to @NicMendonca (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 @MonilBhavsar (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.

[BlameGPT]

Possible culprit PRs for this issue

• fix: expense can be moved to report of deleted workspace #62583: high semantic score.
• fix: workspace change system message shows previous IOU report as long ID (undefined) #62466

Please 👍 or 👎

actual: #58020