[Due for payment 2025-07-01] Reports - After unholding all the expenses, "Hold" label still remains on one of the expenses

[mitarachim]

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.1.48-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): jsdijnsodijoi111@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Go to 1:1 DM.
3. Submit two expenses to the user.
4. Go to Reports.
5. Go to Expense Reports.
6. Select all expenses via checkbox.
7. Click dropdown button.
8. Click Hold.
9. Enter reason and save it.
10. Select all expenses via checkbox.
11. Click dropdown button.
12. Click Unhold.

Expected Result:

"Hold" label will be removed from all the expenses.

Actual Result:

"Hold" label still remains on one of the expenses.

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

Bug6838629_1747859607633.20250522_043057.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @kadiealexander

[melvin-bot]

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

[mollfpr]

I don't think this needs to be a blocker. The issue seems already shows in production with slightly different step.

Screen.Recording.May.22.2025.mp4