[Due for payment 2025-11-12] Workspace - Delete modal persist displayed despite the Workspace is deleted

[nlemma]

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: v9.2.35.0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13177080/test-cases/41237957
Email or phone of affected tester (no customers): na
Issue reported by: Applause Internal Team
Device used: Win11/Chrome, Hybird IOS and OS
App Component: Workspace Settings

Action Performed:

Precondition: user have several workspace

1. Open the link www.staging.new.expensify.com
2. User logged in Owner workspace
3. Navigate to Workspaces
4. Tap on 3 dot next to any Workspace
5. Select "Delete" button (observed that the WS is deleted , but the modal still displayed)

Expected Result:

After user clicked Delete button, the Delete modal should be disappeared

Actual Result:

After user clicked the delete button, the WS is disappeared, but the modal still displayed.

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

Bug6980450_1761039599057.Recording__2279.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @RachCHopkins

[melvin-bot]

Triggered auto assignment to @RachCHopkins (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]

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

[melvin-bot]

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

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

[francoisl]

Investigating this. I can repro locally on tag v9.2.34-2 with main Web-E code, so I'm wondering if it's a backend issue 🤔 Reviewing recent checklists now.

[francoisl]

This is a weird one, I can still repro locally on Web-E's production branch, NewDot's 9.2.34-2 production tag, and on an 7-day commit from Auth. I think it's some sort of race condition. Also can't reproduce on staging with a fresh account:

Screen.Recording.2025-10-21.at.10.57.50.mov

Looking into older suspicious PRs that are already on production, starting with 64015.