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
Can't set distance rate on a new workspace, Oops... something went wrong error appears #39341
Version Number: 1.4.58-2 Reproducible in staging?: y Reproducible in production?: n If this was caught during regression testing, add the test name, ID and link from TestRail: n/a Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: applause internal team Slack conversation:
Action Performed:
Log in with a new expensifail account
Create a new workspace
Enable distance rates in the More features tab
Navigate to Distance rates
Tap on the distance rate
Tap on the rate
Change the rate and save it
Expected Result:
I should be able to set a new rate without errors.
Actual Result:
I can't set distance rate on a new workspace, "Oops... something went wrong" error appears when I try. Sometimes I get a Hmm... it's not here" error when trying to open the rate.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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 it should, yes. This is related to the new collect workspaces being created. I'm guessing the backend is throwing an error. Can someone please get the requestID of the failed API call or at least post the login of the account you used to reproduce the issue?
The account I used earlier today was jkaufman+18@expensifail.com. However, I'm trying to get a requestID for a new attempt and I can't reproduce this now on staging any longer. @tgolen are you still able to reproduce it?
Activity
melvin-bot commentedon Mar 31, 2024
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Mar 31, 2024
Triggered auto assignment to @deetergp (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Mar 31, 2024
👋 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:
joekaufmanexpensify commentedon Apr 1, 2024
@deetergp do you think this should be a deploy blocker? I can reproduce
tgolen commentedon Apr 1, 2024
I think it should, yes. This is related to the new collect workspaces being created. I'm guessing the backend is throwing an error. Can someone please get the requestID of the failed API call or at least post the login of the account you used to reproduce the issue?
joekaufmanexpensify commentedon Apr 1, 2024
Yep, one sec!
joekaufmanexpensify commentedon Apr 1, 2024
The account I used earlier today was jkaufman+18@expensifail.com. However, I'm trying to get a requestID for a new attempt and I can't reproduce this now on staging any longer. @tgolen are you still able to reproduce it?
tgolen commentedon Apr 1, 2024
I wasn't able to reproduce it. You can see here that I changed the default rate to
0.672as well as add a new rate:joekaufmanexpensify commentedon Apr 1, 2024
Cool. Yeah it worked for me on two different accounts just now too.
tgolen commentedon Apr 1, 2024
I guess since neither of us can reproduce it, I'll close this for now. Thank you, Joe!
joekaufmanexpensify commentedon Apr 1, 2024
Course!