Undelete button is disabled on expense row, but expense can be undeleted by bulk select

[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.3.60-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: #86938
Email or phone of affected tester (no customers): soidnjsoidjoisjdiosj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• Have a deleted expense.

1. Go to staging.new.expensify.com
2. Go to Reports > Expenses.
3. Click filters > Status > select Deleted > Save > View results.
4. Click Display > Edit columns, select "Action", and click Save.
5. Go offline.
6. Click Undelete button on the expense row.
   → Undelete button is disabled on the expense row.
7. Select the expense via checkbox.
8. Click dropdown button > Undelete.
   → Expense can be undeleted via bulk selecting.

Expected Result:

In Step 6 and 8, Undelete button should behave the same on expense row and bulk selecting in offline mode.

Actual Result:

In Step 6. Undelete button is disabled on the expense row.
In Step 8, expense can be undeleted via bulk selecting.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7131053_1776311813654.4.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[OSBotify]

Investigation Summary: Frontend bug. Causing PR is 86938 (Deleted transactions on search V2) by @jnowakow. High confidence. Recommendation: REVERT. The causing PR introduced inconsistent offline behavior for the per-row Undelete button vs the bulk Undelete action. Root Cause: In ActionCell/index.tsx at line 92, all non-VIEW/PAY actions including UNDELETE are rendered with isDisabled={isOffline || shouldDisablePointerEvents}. The undelete operation via changeTransactionsReport uses Onyx optimistic updates and works offline, but the button is blocked by this offline check. By contrast, the bulk action path in useSearchBulkActions.ts has no offline guard for UNDELETE - it calls undeleteTransactions() directly. Files modified by PR 86938 that are relevant: ActionCell/index.tsx, useUndeleteTransactions.ts (new), useSearchBulkActions.ts, SearchList/index.tsx. Assigned: @jnowakow (author), @rojiphil (approving reviewer), @luacmartins (approving reviewer). Label update: Keeping DeployBlockerCash, removing DeployBlocker.