"Rate not valid for this workspace" is shown on expense preview but missing in expense thread

[mitarachim]

Held on #72230

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.29-1
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-1237/folder/13176730/41237114/945416708
Email or phone of affected tester (no customers): sdiojnjsdosjodsj@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 workspace chat
3. Create a distance expense
4. Open the transaction thread
5. Click Report
   6.Click Remove from report
6. Go to self DM
7. Open the expense thread

Expected Result:

"Rate not valid for this workspace" will be shown on expense preview and expense thread

Actual Result:

"Rate not valid for this workspace" is shown on expense preview but missing in expense thread

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

Bug6970872_1760107510500.Screen_Recording_2025-10-10_at_22.41.00.mp4

View all open jobs on GitHub

[melvin-bot]

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

[ikevin127]

🔄 I ran Vector¹ on this deploy blocker issue and here are the top 3 possible offending PRs based on semantic similarity²:

• #71891: Enable create report option for unreported expenses
• #71910: When admin becomes a member, #admins leads to Not here, skeleton loading in Inbox
• #72094: Create transaction thread for unreported transactions

Please drop a 👍 (correct) or 👎 (incorrect) as feedback regarding the results (will use to fine-tune the reranking model).

Note

PR # and name added as text only to avoid triggering regression automation on the issues which the above PRs are addressing in case the finding is incorrect.

Footnotes

1. Vector is currently a local-only prototype stage app that uses AI embeddings to find offending PRs for a given deploy blocker issue. Because of the early stage of the app, results must be taken with with a grain of🧂. How it works: grab deploy blocker issue's OP data (title, steps, expected / actual result) and embed -> grab all deploy checklist issue PRs data (title, explanation of change, tests, changed files, AI diff summary) and embed -> calculate cosine similarity of issue embedding to each PRs embedding -> get results -> perform reranking -> get final results. ↩

2. Semantic similarity, when applied to embeddings, measures the similarity in meaning between different pieces of text by comparing their vector representations in a high-dimensional "semantic space". Texts with similar meanings are mapped to vectors that are close together, and this "closeness" is quantified using metrics like cosine similarity. This technology enables search engines and chatbots to find relevant information even without exact keyword matches, providing more accurate and contextualized results. ↩