Workspace - Error on Employee workspace chat when Admin remove it from workspace

[lanitochka17]

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: 1.4.25-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
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:

1. Login as Admin
2. Navigate to Workspace> invite members page
3. Invite user B
4. Remove user B
5. Login as user B
6. Navigate to the workspace chat

Expected Result:

Workspace chat should be archived and there should no be error messages

Actual Result:

"Policy does not exist or you do not have access. Try refreshing the page." error message appears on Employee workspace chat when Admin remove it from Workspace

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6343660_1705356959996.Recording__1811.mp4

View all open jobs on GitHub

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

[melvin-bot]

Triggered auto assignment to @cead22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[cead22]

@lanitochka17 can you check what API call triggered the error? And just to confirm, this can't be reproduced in production?

[cead22]

Per discussion in this thread https://expensify.slack.com/archives/C01GTK53T8Q/p1705364273810119?thread_ts=1705357942.034469&cid=C01GTK53T8Q, I'm going to close this and open a deploy blocker issue in E/E since this seems to be a backend problem