LHN - "Owes 0,00" remains displayed on chat preview on LHN after deleting an empty report.

[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.3.11.17
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3952/folder/13176730/41237110/1160416952?issue_type=jira
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.
Prerequisite 2: No expenses created on workspace yet and no messages sent.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create a new empty report.
4. Right click on the just created report and delete it.
5. Note that "Owes 0,00" appears on chat preview on LHN and remains displayed until navigating to a different chat and returning.

Expected Result:

After deleting an empty report, chat preview should display a "This is where user will submit expenses" message if report had no previous messages.

Actual Result:

After deleting an empty report, "Owes 0,00" appears on chat preview and remains displayed until navigating to a different chat and returning to workspace.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #80343 - "Reverted new Onyx Derived Value VISIBLE_REPORT_ACTIONS, blockers fix" by @BartekObudzinski (High confidence)
Related Issues: None found

Recommendation: ROLL FORWARD

This PR introduced significant changes to report action visibility computation in the LHN, affecting how preview messages are generated. While this is a cosmetic bug that does not prevent core functionality, rolling forward with a focused fix is recommended since:

1. PR Reverted new Onyx Derived Value VISIBLE_REPORT_ACTIONS, blockers fix #80343 contains important blocker fixes for the previous deploy
2. The bug is a display issue - the incorrect "Owes 0,00" message eventually clears when navigating away
3. A targeted fix to handle deleted report preview messages in workspace chats would be safer than reverting

Labels: Keeping DeployBlockerCash (Frontend bug requires App changes)

Detailed Analysis

Evidence

PR #80343 was merged on Jan 30, 2026 at 20:05 UTC and is included in the staging deploy checklist. This PR fundamentally changed how report actions visibility is computed by introducing a derived Onyx value VISIBLE_REPORT_ACTIONS. The PR modified key LHN files including:

• src/components/LHNOptionsList/LHNOptionsList.tsx
• src/libs/OptionsListUtils/index.ts
• src/libs/SidebarUtils.ts

The changes affect how getLastMessageTextForReport and getAlternateText compute preview messages, particularly for workspace chats with report preview actions.

Verification

The affected area is the LHN preview text generation for workspace chats. Key files modified by PR #80343:

• src/components/LHNOptionsList/LHNOptionsList.tsx (44 additions, 44 deletions)
• src/libs/OptionsListUtils/index.ts (180 additions, 94 deletions)

These files handle the logic for computing the alternate text shown in the LHN, which is where the bug appears.

Root Cause

When a report is deleted from a workspace chat, the LHN should fall back to showing the default workspace message ("This is where user will submit expenses"). However, the new visibility computation logic in PR #80343 appears to be incorrectly retaining or computing a preview message from a deleted report action, showing "Owes 0,00" instead.

The issue is timing-related: the preview text is cached or computed from stale report action data immediately after deletion, but gets corrected when the component re-renders after navigating away and back (when fresh data is fetched).

The specific issue likely lies in how getLastMessageTextForReport handles report preview actions when the underlying report has been deleted, combined with how the new visibleReportActionsData derived value caches visibility state.