[Due for payment 2026-09-09] Workspace - Auto categorization settings is not disabled in the duplicated workspace

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

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories > Settings.
3. Disable Auto-categorize new expenses.
4. Go back to workspace list.
5. Click 3-dot menu on the workspace > Duplicate workspace > Next > Continue.
6. Open duplicated workspace settings > Categories.
7. Click Settings.

Expected Result:

Auto categorization settings will be disabled in the duplicated workspace.

Actual Result:

Auto categorization settings is not disabled in the duplicated workspace.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7248548_1788310485296.2.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @mallenexpensify

[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/56fe1a350be926ad5fc0e7e75b7223fc85ad610686b8d0849eb2b34551478b00

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

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

[melvin-bot]

@heyjennahay @jasperhuangg @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #98030

[melvin-bot]

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

[melvin-bot]

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