[$250] "Not Found" page flash after deleting expense

[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: v9.3.26-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79530
Email or phone of affected tester (no customers): applausetester+ds@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 14.5/ Chrome
App Component: Money Requests

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Go to a chat and create a single expense
3. Open the expense
4. Click the report details (header)
5. Delete the expense from the details page

Expected Result:

Navigates back smoothly, no "Not Found" flash, no errors

Actual Result:

"Not Found" page flash when navigates back

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7088623_1772052012444.Screen_Recording_2026-02-25_at_11.29.09_at_night.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jayeshmangwani

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022026850578182079486
• Upwork Job ID: 2026850578182079486
• Last Price Increase: 2026-02-26

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #79530

[melvin-bot]

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

[melvin-bot]

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

[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.