WEB - "not found page" not shown when returning to self DM from deleted expense

[lanitochka17]

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.79-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #65622
Issue reported by: Applause - Internal Team

Action Performed:

Precondition: Have a WS chat with a non-empty report.

1. Go to ND
2. Go to self dm
3. Submit track expense
4. Submit that expense to the report in the WS
5. Delete the expense you just submitted to the report
6. Go back

Expected Result:

"Not found page" should be displayed while trying to return to self dm from a deleted expense

Actual Result:

User goes back to self dm directly

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6883577_1752150620792.Screen_Recording_2025-07-10_at_14.11.19.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @clarajones-expensify (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.

[clarajones-expensify]

Looks like this PR (#65622) is related to this bug

[bernhardoj]

The step is different from #65622, but the QA expects the same expected result as #65622. There is no reason for the not found page to show here.

[clarajones-expensify]

Thanks @bernhardoj ! So this issue (#65853) is a valid bug that should be fixed?

[bernhardoj]

I personally don't think this is a bug at all.

[clarajones-expensify]

Sounds good, closing this out then.