Card - Broken connection error fails to appear after clicking simulate a broken connection

[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: 9.3.60-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - it is related to a bank account flow and the "Break connection" feature is not available on prod.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #87553
Email or phone of affected tester (no customers): applausetester+bm8905@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Web, android
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com
2. Connect a company card feed with the mock bank connection
3. Assign a card
4. Tap the card row
5. Click simulate a broken connection
6. Repeat the simulation several times to check for consistency

Expected Result:

Broken connection banner should consistently appear at the top of the page

Actual Result:

Broken connection banner does not appear or appears inconsistently

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7131162_1776320841405.bandicam_2026-04-16_09-22-38-886.mp4

View all open jobs on GitHub

[melvin-bot]

@marcochavezf recently merged #87553, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[OSBotify]

Investigation Summary - Classification: Frontend bug - Causing PR: #87553 (High confidence) - Recommendation: REVERT - Labels: DeployBlockerCash kept, DeployBlocker retained. Assigned: @marcochavezf @hungvu193 @joekaufmanexpensify. PR 87553 ("Hide duplicate card row error when feed connection is broken", merged 2026-04-15) introduced the regression. It added a condition "assignedCard?.pendingFields?.lastScrape ? undefined : assignedCard?.errors" to suppress card-row errors. The broken connection banner in WorkspaceCompanyCardsTableHeaderButtons only shows when isFeedConnectionBroken === true, but the new condition hides errors as soon as pendingFields.lastScrape is set, even before isFeedConnectionBroken becomes true. This creates a timing window where neither the card-row error nor the top-level banner is visible, causing the inconsistent/missing banner behavior. The only file changed is src/pages/workspace/companyCards/WorkspaceCompanyCardsTable/index.tsx.