[$250] Approvals - Incorrect Approval Flow After Reverting Approval Order

[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.1.59-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #63326
Email or phone of affected tester (no customers): applausetester+dp166owner@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows / Chrome
App Component: Other

Action Performed:

1. Employee submits Report 1 with 1 expense.
2. Current approval order: Employee > Approver A > Approver B
3. Owner/Admin changes the approval order to: Employee > Approver C > Approver B
4. Employee submits Report 2 with 1 expense. New approval flow should be: Employee > Approver C > Approver B
5. Owner/Admin changes the approval order back to: Employee > Approver A > Approver B
6. Approver C Approves Report 2.
7. Employee checks the report status and sees that Approver A now needs to approve.
8. Approver A has the Approve button active for Report 2.

Expected Result:

Report 2 should continue through the original approval flow it was submitted under: Employee > Approver C > Approver B
After Approver C approves, the report should route to Approver B, not Approver A.
Approver A should not be part of Report 2’s flow at any point.

Actual Result:

After Approver C approves Report 2:
The report routes to Approver A instead of Approver B.
Approver A has the Approve button enabled.
The approval flow now incorrectly looks like:
Employee > Approver C > Approver A > Approver B

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

Bug6851157_1749093262654.video_71.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021930996480135360590
• Upwork Job ID: 1930996480135360590
• Last Price Increase: 2025-06-20

Issue Owner

Current Issue Owner: @allroundexperts

[melvin-bot]

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

Job added to Upwork: https://www.upwork.com/jobs/~021930996480135360590

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External)

[melvin-bot]

@allroundexperts Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@allroundexperts Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@allroundexperts 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!