[Due for payment 2026-03-13] [$250] Distance - Expense preview and report header shows "Pending..." after changing amount

[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.3.28-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: #74967
Email or phone of affected tester (no customers): isodjnosidjiojiojiso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Create a manual distance expense.
4. Open the expense.
5. Click Amount.
6. Edit amount and save it.
7. Go back to self DM.

Expected Result:

Expense preview and report header will not show "Pending..." after changing amount.

Actual Result:

Expense preview and report header shows "Pending..." after changing amount.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7092360_1772491855122.4.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dylanexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022028617050045362994
• Upwork Job ID: 2028617050045362994
• Last Price Increase: 2026-03-02
• Automatic offers:
• FitseTLT | Reviewer | 110642776

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #74967 - "Fix - [Unreported] Add distance rate to the distance expenses tracked in selfDM" by @FitseTLT (High confidence)
Related Issues: None

Recommendation: REVERT

The PR introduced changes to how distance rates are handled for track expenses in self DM, which is causing the "Pending..." status to persist after editing the amount of a distance expense. Reverting this PR will restore the previous behavior and resolve the issue.

Labels: Keeping DeployBlockerCash (App deploy is blocked). Issue is not reproducible on production, only staging.

📋 Detailed Analysis

Evidence

• The issue is reproducible on staging but NOT on production
• The issue report explicitly links to PR Fix - [Unreported] Add distance rate to the distance expenses tracked in selfDM #74967
• The bug appears when editing the amount field of a manual distance expense in self DM
• PR Fix - [Unreported] Add distance rate to the distance expenses tracked in selfDM #74967 was merged on 2026-02-28, and is included in the current staging deploy (9.3.28-0)

Verification

PR #74967 modified multiple files related to distance expense handling, including:

• src/components/ReportActionItem/MoneyRequestView.tsx - Added isTrackExpense support for distance/rate editing
• src/libs/actions/IOU/index.ts - Changed how policyForMovingExpenses is used for track expenses
• src/libs/DistanceRequestUtils.ts - Modified rate calculation logic for track expenses
• src/hooks/usePolicyForTransaction.ts - Added support for policyDraft parameter

The specific issue occurs because:

1. PR Fix - [Unreported] Add distance rate to the distance expenses tracked in selfDM #74967 changed how distance rates are calculated and stored for track expenses in self DM
2. When editing the amount of a distance expense, the UI checks for pending actions on both amount and customUnitRateID fields (line 858 in MoneyRequestView.tsx)
3. The changes introduced in Fix - [Unreported] Add distance rate to the distance expenses tracked in selfDM #74967 appear to be setting a pending state on customUnitRateID that does not properly clear after the amount update completes
4. This causes the "Pending..." indicator to show in both the expense preview and report header

Root Cause

The PR introduced complex logic for handling distance rates in track expenses that involves:

• New parameters (policyForMovingExpenses, isTrackDistanceExpense)
• Changes to rate calculation in DistanceRequestUtils.getRate()
• Modified handling of customUnitRateID for unreported expenses

When a user edits the amount of a distance expense in self DM, the system attempts to recalculate the rate, but the pending field for customUnitRateID is not being properly cleared, causing the UI to display "Pending..." indefinitely.