[Search v1] - Action field remains as "Paid" after expenses are unapproved until page is revisited

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.5-4
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:

1. Go to staging.new.expensify.com
2. Go to workspace chat as admin
3. Submit two expenses
4. Go to Search > Shared
5. Click on the grouped expenses
6. Pay elsewhere the expense
7. Go back to Search > Shared
8. Click on the grouped expenses
9. Click on the report header
10. Click Unapprove

Expected Result:

The action field for the grouped expenses will turn to "Action"

Actual Result:

The action field for the grouped expenses remains "Paid", until the Search page is revisited

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

Bug6536222_1720466433439.20240709_031521.mp4

View all open jobs on GitHub

[melvin-bot]

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

@tylerkaraszewski FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

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

[mountiny]

cc @luacmartins

[luacmartins]

hmm this is a tricky one. We save the action in its own key in snapshot_ so the live updates don't change this key since the live onyx data, e.g. report_ and transactions_ don't have the action key.

[luacmartins]

This is not a blocker though since I was able to reproduce in production.

[melvin-bot]

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

[melvin-bot]

@tylerkaraszewski Still overdue 6 days?! Let's take care of this!

[melvin-bot]

@tylerkaraszewski Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[tylerkaraszewski]

@luacmartins - do you think we can make this external, or are you interested in working on it?

[luacmartins]

I can't reproduce this exact issue anymore since I don't see an option to Unapprove. I can reproduce with the Cancel payment option.

This happens because we update the report's statusNum in Onyx and computing the new state when cancelling the payment, but the Search page uses the action key computed on the server to determine what the next action should be. I'm not really sure how to solve since it'd require a fundamental change to the Search design.

[melvin-bot]

Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

Still overdue 6 days?! Let's take care of this!

[melvin-bot]

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

[tylerkaraszewski]

@luacmartins What do you think should we just close this then?

[luacmartins]

Yea, I think we can close this for now.