[$250] Workflow - The removed second approver reappears after navigating back to edit approval page

[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: 9.2.96-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 BrowserStack: #78350
Email or phone of affected tester (no customers): applausetester+bm1021@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Web, mweb, android
App Component: Workspace Settings

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Create a workspace and add three members(employee, approver A, approver B)
3. Create an approval workflow where the employee submits to approver A, and approver B is the second approver
4. Open the created workflow
5. Click on Second Approver > Approver > deselect approver B > Save
6. Click on Approver field > Save

Expected Result:

the second approver should remain removed

Actual Result:

After clicking Save in the first approver field and returning to the Edit Approval Workflow page, the removed second approver reappears.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7043985_1767904845437.bandicam_2026-01-08_23-26-14-466.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022010706674344890012
• Upwork Job ID: 2010706674344890012
• Last Price Increase: 2026-01-21

Issue Owner

Current Issue Owner: @

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #78350

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @greg-schroeder (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.

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

[abzokhattab]

I think its not caused by the changes we made. i am able to reproduce the same bug on prod:

Screen.Recording.2026-01-08.at.22.13.39.mov

what do u think? @JS00001 is it a blocker?

that said i dont mind fixing it in a follow up PR