Expense - Category field does not show "Category no longer valid" when category is deleted

[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.18-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #70821
Email or phone of affected tester (no customers): ksdpokpsomkspopskd@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has self DM and a default workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Create a track expense.
4. Open transaction thread.
5. Click Category and select a category.
6. Go to workspace settings > Categories.
7. Delete the category selected in Step 5.
8. Go back to self DM.
9. Open transaction thread.

Expected Result:

Category field will show "Category no longer valid" because the selected category is deleted.

Actual Result:

Category field does not show "Category no longer valid" when the selected category is deleted.

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

Bug6954958_1758756368120.Screen_Recording_2025-09-25_at_07.23.45.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @koko57

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

[melvin-bot]

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

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

[melvin-bot]

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