Workspace - Archived workspace not displayed

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.61-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: #97778
Email or phone of affected tester (no customers): applausetester+mnh@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Win 11 / chrome
App Component: Workspace Settings

Action Performed:

Requirement: Have an account with archived workspaces where user is admin.

1. Open the Workspaces tab.
2. Verify that only active workspaces are displayed by default.
3. Click the Filter button in the top-right corner and select Archived.
4. Verify that only archived workspaces are displayed.

Expected Result:

only archived workspaces are displayed.

Actual Result:

No results found
No results. Please try adjusting your filters or search query

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7242794_1787695914256.Recording__3429.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7242794

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/2c72a855e43981257a5f4b293a02e8a599e6fb132e5df794ba33ba3332753a96

[melvin-bot]

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

[melvin-bot]

@rlinoz @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #97778

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

@truph01 you have been assigned to this deploy blocker because you authored the offending PR: #97778

[melvin-bot]

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

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #97778 - "[Release 4] feat: Add the Active/Archived filter to the Workspaces tab" by @truph01 (High confidence)
Related Issues: #97122 (feature request implemented by the PR)

Recommendation: REVERT

PR #97778 introduces the exact Active/Archived filter that is broken, and the feature is non-functional end-to-end because the archived-policy data it filters on never reaches the client. Since it is gated behind the ARCHIVE_POLICIES beta (so blast radius is limited to beta users and it is N/A in production), reverting #97778 cleanly unblocks the App deploy; the feature can re-land once archived workspaces are actually delivered to the client. (Equivalent low-risk alternative: keep the ARCHIVE_POLICIES beta disabled.)

Assigned: @truph01 (PR author), @rlinoz and @daledah (approving reviewers) — already assigned to this issue
Labels: No change. DeployBlockerCash is kept (an App PR caused the regression and it is not reproducible in production). DeployBlocker is not present, so nothing is removed.

📋 Detailed Analysis

Evidence

• PR [Release 4] feat: Add the Active/Archived filter to the Workspaces tab #97778 (merged 2026-08-25, in the current StagingDeployCash #99466) is titled "Add the Active/Archived filter to the Workspaces tab" and adds the Active/Archived multi-select filter to the Workspaces list — precisely the control that returns "No results found" when Archived is selected.
• Reproducible on staging, N/A in production because the whole filter is new — consistent with a regression introduced by this PR rather than a pre-existing backend fault.
• The PR diff adds no API/read command to fetch archived policies and never writes archivedDate; it only adds client-side filtering over the policies already in Onyx.

Verification

• The filter option values and matching live in src/components/Tables/WorkspaceListTable/index.tsx (isItemInFilter, lines 147-165, and filterConfig, lines 167-185). Selecting Archived produces filterValues = ['archived']; a row is kept only when filterValues.includes(ARCHIVED) && item.isArchived (line 160).
• item.isArchived is populated in src/pages/workspace/WorkspacesListPage.tsx:159 from policy.isArchived, which the selector createWorkspaceListPoliciesSelector sets via isArchivedPolicy(policy) (src/selectors/Policy.ts:98-107).
• isArchivedPolicy is !!policy?.archivedDate (src/libs/PolicyUtils.ts:101-103). archivedDate is documented as the single source of truth and is absent when the policy is active (src/types/onyx/Policy.ts:2877-2878).
• Confirmed via gh pr diff 97778: the PR modifies exactly these files (WorkspaceListTable/index.tsx, selectors/Policy.ts, PolicyUtils.ts, WorkspacesListPage.tsx, plus shared Table components), and its merge date aligns with when the bug appeared on staging.

Root Cause

The Archived filter is correct in isolation, but it filters on isArchivedPolicy(policy) → !!policy.archivedDate. The tester's archived workspaces reach the list with no archivedDate populated (archived policies are not being delivered to the client with that field / not loaded into the POLICY collection), so every row evaluates item.isArchived === false. Selecting Archived therefore matches zero rows and the table renders its no-results state (processedData.length === 0 in src/components/Table/Table.tsx:367).

PR #97778 shipped the UI filter without the underlying archived-policy data being available on the client, so the feature cannot work as-is. Per the deploy-blocker classification, a feature an App PR ships before the data layer supports it is a Frontend bug and the App PR should be reverted.

---

view run