You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Rate not valid for this workspace" error after deleting the rate in Duplicated Workspace #69835
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:
Sign in to ND with expensifail account
Create a workspace, add a new distance rate
Create a distance expense with a new rate
Navigate to the Workspaces tab, duplicate the workspace including distance rates
Open the duplicate workspace settings and delete the new rate
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/a I don't think this is a regression.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/a
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Create a workspace, add a new distance rate
Create a distance expense with a new rate
Navigate to the Workspaces tab, duplicate the workspace including distance rates
Open the duplicate workspace settings and delete the new rate
Navigate to the chat of the original workspace, observe the distance expense preview
Verify that there is no error shown on the expense report
changed the title [-][Due for payment 2025-09-26] [Due for payment 2025-09-23] "Rate not valid for this workspace" error after deleting the rate in Duplicated Workspace[/-][+]"Rate not valid for this workspace" error after deleting the rate in Duplicated Workspace[/+]on Oct 14, 2025
Activity
melvin-bot commentedon Sep 4, 2025
Triggered auto assignment to @amyevans (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 4, 2025
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 commentedon Sep 4, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 4, 2025
👋 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:
narefyev91 commentedon Sep 4, 2025
Feature is under the beta - I will check this one
narefyev91 commentedon Sep 4, 2025
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
amyevans commentedon Sep 4, 2025
Thanks @narefyev91, I'll demote it and assign you. @mountiny you want this one?
45 remaining items
mallenexpensify commentedon Oct 7, 2025
@getusha plz complete the BZ checklist. and.. you due payment here!?
getusha commentedon Oct 8, 2025
Oh yes. working on it!
getusha commentedon Oct 8, 2025
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/a I don't think this is a regression.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/a
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Oct 13, 2025
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Oct 13, 2025
@mallenexpensify Huh... This is 4 days overdue. Who can take care of this?
mallenexpensify commentedon Oct 13, 2025
Test case created
@getusha are you due payment here? If so, I'm assuming $250.
getusha commentedon Oct 14, 2025
Yes and yes, there isn't a regression i am aware of.
[-][Due for payment 2025-09-26] [Due for payment 2025-09-23] "Rate not valid for this workspace" error after deleting the rate in Duplicated Workspace[/-][+]"Rate not valid for this workspace" error after deleting the rate in Duplicated Workspace[/+]mallenexpensify commentedon Oct 14, 2025
Payment Summary
Contributor+: @getusha due $250 via NewDot
twisterdotcom commentedon Oct 16, 2025
@getusha has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-1386-a202-9f56-7b04cc128dd1