"Rate not valid for this workspace" error after deleting the rate in Duplicated Workspace

[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.2.1-11
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: #69146
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.6 Chrome, iPhone 15 iOS 18.6 Safari
App Component: Money Requests

Action Performed:

1. Sign in to ND with expensifail account
2. Create a workspace, add a new distance rate
3. Create a distance expense with a new rate
4. Navigate to the Workspaces tab, duplicate the workspace including distance rates
5. Open the duplicate workspace settings and delete the new rate
6. Navigate to the chat of the original workspace, observe the distance expense preview

Expected Result:

"Rate not valid for this workspace" error is not shown, when the rate is deleted in another workspace

Actual Result:

"Rate not valid for this workspace" error is displayed on the distance expense preview in the original WS chat after deleting the rate in the Duplicate WS. The same issue occurs, if the expense created in the Duplicate WS, and the rate is deleted in the original WS. The error is displayed in the expense details after opening, then disappears.

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

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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]

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

[narefyev91]

Feature is under the beta - I will check this one

[narefyev91]

I think the problem is that customUnitID and customUnitRateID ID's a copied for duplicated workspace 1:1 (and not created with uniques).
This is screen with old expense with customUnitID and customUnitRateID:

When i remove tag from new duplicated workspace - id's are exactly the same:

Which leads to transaction violation updates - which come from Onyx. cc @mountiny
Anyway issue could be unchecked - it's under Beta flag

Screen.Recording.2025-09-04.at.13.11.49.mov