Held expense - Header subtitle in system message thread opens not here page when holding fails

[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.0.15-5
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• User A and B have no unsettled expense

1. Go to staging.new.expensify.com
2. [User A] Submit an expense to User B
3. [User A] Click on the preview in the main chat to go to combined report
4. [User A] Click on the report header > Hold
5. [User A] Leave Hold RHP open
6. [User B] Pay the expense
7. [User A] Enter a reason to hold and save it
8. [User A] Right click on "held this expense" system message > Reply in thread
9. [User A] Click on the header subtitle

Expected Result:

App will redirect to the transaction thread when clicking on the header subtitle (production behavior)

Actual Result:

App opens not here page when clicking on the header subtitle

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6559349_1722527042381.20240801_233602.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[lanitochka17]

Production:

Recording.2273.mp4

[Beamanator]

Logs - error:

403 Transaction not accessible