Workflows - Removed member is still shown in description and additional approver field

[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: 9.2.86-0
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: #76032
Email or phone of affected tester (no customers): sdjoisdjnoidsjdsoi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• User has invited another user to the workspace.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Workflows.
3. Click on the default workflow.
4. Click Approver.
5. Add report amount.
6. Click Additional approver.
7. Select the invited member.
8. Click Save > Save.
9. Go to Members and remove the invited member.
10. Go back to Workflows.
11. Open the default workflow.
12. Click Approver > Additional approver.

Expected Result:

After removing additional approver, limit description should update and Additional approver field should be cleared.

Actual Result:

After removing additional approver, limit description and Additional approver field still show the removed member.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7035783_1766469901092.12.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[abzokhattab]

we didnt discuss this flow ... what should happen if the user removes a user? should we remove the whole workflow or should we only remove the additional approver and the limit?

@JmillsExpensify @JS00001

[abzokhattab]

I think this would also need BE changes as well