Skip to content

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

Closed

Description

@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 OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 4, 2025
  2. melvin-bot commented on Sep 4, 2025

    @melvin-bot

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

  3. melvin-bot commented on Sep 4, 2025

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

  4. melvin-bot commented on Sep 4, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 4, 2025

    @github-actions
    Contributor

    👋 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.
  6. narefyev91 commented on Sep 4, 2025

    @narefyev91
    Contributor

    Feature is under the beta - I will check this one

  7. narefyev91 commented on Sep 4, 2025

    @narefyev91
    Contributor

    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:

    Image

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

    Image

    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
  8. amyevans commented on Sep 4, 2025

    @amyevans
    Contributor

    Thanks @narefyev91, I'll demote it and assign you. @mountiny you want this one?

  9. 45 remaining items

  10. mallenexpensify commented on Oct 7, 2025

    @mallenexpensify
    Contributor

    @getusha plz complete the BZ checklist. and.. you due payment here!?

  11. getusha commented on Oct 8, 2025

    @getusha
    Contributor

    @getusha plz complete the BZ checklist. and.. you due payment here!?

    Oh yes. working on it!

  12. getusha commented on Oct 8, 2025

    @getusha
    Contributor

    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:

    1. Create a workspace, add a new distance rate
    2. Create a distance expense with a new rate
    3. Navigate to the Workspaces tab, duplicate the workspace including distance rates
    4. Open the duplicate workspace settings and delete the new rate
    5. Navigate to the chat of the original workspace, observe the distance expense preview
    6. Verify that there is no error shown on the expense report

    Do we agree 👍 or 👎

  13. melvin-bot commented on Oct 13, 2025

    @melvin-bot

    @mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

  14. melvin-bot commented on Oct 13, 2025

    @melvin-bot

    @mallenexpensify Huh... This is 4 days overdue. Who can take care of this?

  15. mallenexpensify commented on Oct 13, 2025

    @mallenexpensify
    Contributor

    Test case created

    @getusha are you due payment here? If so, I'm assuming $250.

  16. getusha commented on Oct 14, 2025

    @getusha
    Contributor

    @getusha are you due payment here? If so, I'm assuming $250.

    Yes and yes, there isn't a regression i am aware of.

  17. 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
  18. mallenexpensify commented on Oct 14, 2025

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @getusha due $250 via NewDot

  19. twisterdotcom commented on Oct 16, 2025

    @twisterdotcom
    Contributor

    @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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions