-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reports - Report name is "Unavailable workspace" after workspace is deleted #56580
Comments
Triggered auto assignment to @johncschuster ( |
Triggered auto assignment to @AndrewGable ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
🚨 Edited by proposal-police: This proposal was edited at 2025-02-08 21:20:53 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Report name is "Unavailable workspace" after workspace is deleted What is the root cause of that problem?Here Line 1066 in 631006e
We try to get the policy from Params policy ?? policies?.find((p) => p.id === report.policyID) that indeed return the policy when available but as soon the policy get deleted our first value Due to this What changes do you think we should make in order to solve the problem?we should explicitly check if const finalPolicy = isEmptyObject(policy) ? allPolicies?.[`${ONYXKEYS.COLLECTION.POLICY}${report.policyID}`] : policy ?? policies?.find((p) => p.id === report.policyID); What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?N/A What alternative solutions did you explore? (Optional)We can return undefined for policy when it deleted instead of empty object Results Screen.Recording.2025-02-09.at.2.08.38.AM.mov |
@samranahm - Any ideas which recent changes introduced this? |
Seems like it was introduced in #50135 @luacmartins @zfurtak is this expected behavior? |
Commented in Slack, but I don't think we need to block the deploy on this. Let's remove the label and let @zfurtak work on a follow up fix. |
@zfurtak comment here and @luacmartins can assign you, thank you! |
@luacmartins Proposal here please take a look, thank you |
Here I am 😊 |
@zfurtak @luacmartins Let's see the below image ![]() Some cases still display "unavailable workspace", the reason for these cases is due to the |
@luacmartins I proposed this solution first, would you please take a look |
@samranahm thanks for the interest, but @zfurtak is handling this one as the original author |
Got it, thanks for clarifying @luacmartins
Well, I am trying to find the best possible solution for this edge case and will update here as soon I find one. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.95-1
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: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Search
Action Performed:
Expected Result:
The report name for the deleted workspace should be the name of the workspace.
Actual Result:
The report name for the deleted workspace is "Unavailable workspace".
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6737081_1739022656494.20250208_214633.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: