Report - Default rate still visible for some time after creating expense with different rate

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.52-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: #97517
Email or phone of affected tester (no customers): ibellicotest+2766@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: At least one distance rate created apart from "Default"

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create a map distance expense with a rate different from default.
4. Once expense is created, open report quickly.
5. Note that while expense is still loading, "Default rate" is still visible on "Rate" field.
6. Note that after some time, rate changes to the selected one.

Expected Result:

Distance expense report should automatically display the selected rate.

Actual Result:

"Default Rate" is still visible on report for some time, after creating a map distance expense with a different rate.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7230606_1786407603679.Default.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7230606

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022087931219240475300
• Upwork Job ID: 2087931219240475300
• Last Price Increase: 2026-08-13

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/9cf6d69867c128e783e6208059524509e59d24bce52095bf13490a5a86924c35

[melvin-bot]

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

[melvin-bot]

@Valforte @abdulrahuman5196 you have been assigned to this deploy blocker because you reviewed the offending PR: #97517

[melvin-bot]

@Gonals you have been assigned to this deploy blocker because you authored the offending PR: #97517

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