You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Category Visibility] 1.b.3 [Ring1][Auth] Categories can't be turned off while a member's category visibility is restricted #107057
Version Number: 9.5.40-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:#106674 Email or phone of affected tester (no customers):sjoidjnisojdosn@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:
Precondition:
Create a Control workspace.
Go to staging.new.expensify.com
Go to workspace settings > Members.
Click on your profile.
Click Category visibility.
Unselect any category > Save,
Go to workspace settings > More features.
Disable Categories.
Expected Result:
Categories will be disabled.
Actual Result:
Categories is auto enabled after changing category visibility settings and disabling Categories.
User is not able to disable it.
👋 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:
Identify the pull request that introduced this issue and revert it.
Verification was blocked: dev NewDot displayed a blank page and the browser session reported connection loss. The reported behavior could not be confirmed or disproved through runtime testing.
Step
Status
Create Control workspace and open Members > own profile > Category visibilityBlocked before setup because no app UI rendered.
❌
Unselect a category and successfully SaveNot reached. Source investigation confirms that saving visibility restrictions changes category visibleTo membership: Category.ts:1882–1906.
❌
Disable Categories under More features and check persistenceNot reached in the browser. Investigation finding:Remove the category visibility beta is confirmed as the rollout exposing this flow, not conclusively as the origin of the underlying failure. It removes access gating without changing the disable action. It is included in the 9.5.40-0 staging checklist. Mechanism: The More features switch calls an action that optimistically disables the feature and every category, without transitioning visibility restrictions. Its failure handler explicitly re-enables Categories, matching the reported switch bounce. Recommendation: Keep the deploy blocker and revert the beta-removal rollout to limit further exposure. This restores gating; it does not repair restrictions already saved or fix beta users. Production still has the feature behind its beta gate.
❌
Capture EnablePolicyCategories enabled=false response, jsonCode, and messageNo request was captured. Remaining uncertainty: Backend rejection of disabling restricted categories is the leading hypothesis, not a verified root cause. A server response or subsequent update could also restore the flag. Capture the disable response after a confirmed successful visibility save before choosing a functional fix; do not assume a specific validation error. Confidence is high for rollout attribution, medium for the failure mechanism.
changed the title [-]Categories - Unable to disable Categories after changing category visibility settings[/-][+][Category Visibility] 1.b.3 [Ring1][Auth] Categories can't be turned off while a member's category visibility is restricted[/+]on Nov 16, 2026
The fix for this is in Auth. The PR is merged. It should be deployed tomorrow and then i'll remove the blocker label on this.
If this is the last thing holding up deploy we can revert the beta PR i.e., this or disregard this blocker. I think the latter is fine because this is an edge case and not a common scenario and we have a fix that will go live soon.
Activity
applause-bot commentedon Nov 16, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/6fc1dc58847b63e259eb15e564563b4cefa41109ab560921539e7712a3eaab1f
expensify-chore-bot commentedon Nov 16, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #106674
expensify-chore-bot commentedon Nov 16, 2026
@chiragsalian @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #106674
github-actions commentedon Nov 16, 2026
👋 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:
expensify-chore-bot commentedon Nov 16, 2026
@nkdengineer you have been assigned to this deploy blocker because you authored the offending PR: #106674
expensify-chore-bot commentedon Nov 16, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Nov 16, 2026
🤖 Web test steps verification results: ❌ fail
Verification was blocked: dev NewDot displayed a blank page and the browser session reported connection loss. The reported behavior could not be confirmed or disproved through runtime testing.
Create Control workspace and open Members > own profile > Category visibility
Blocked before setup because no app UI rendered.Unselect a category and successfully Save
Not reached. Source investigation confirms that saving visibility restrictions changes categoryvisibleTomembership: Category.ts:1882–1906.Disable Categories under More features and check persistence
Not reached in the browser.Investigation finding: Remove the category visibility beta is confirmed as the rollout exposing this flow, not conclusively as the origin of the underlying failure. It removes access gating without changing the disable action. It is included in the 9.5.40-0 staging checklist.
Mechanism: The More features switch calls an action that optimistically disables the feature and every category, without transitioning visibility restrictions. Its failure handler explicitly re-enables Categories, matching the reported switch bounce.
Recommendation: Keep the deploy blocker and revert the beta-removal rollout to limit further exposure. This restores gating; it does not repair restrictions already saved or fix beta users. Production still has the feature behind its beta gate.
Capture EnablePolicyCategories enabled=false response, jsonCode, and message
No request was captured.Remaining uncertainty: Backend rejection of disabling restricted categories is the leading hypothesis, not a verified root cause. A server response or subsequent update could also restore the flag. Capture the disable response after a confirmed successful visibility save before choosing a functional fix; do not assume a specific validation error. Confidence is high for rollout attribution, medium for the failure mechanism.
view run · no recording available
chiragsalian commentedon Nov 16, 2026
Looks like a valid bug. The fix for this is in the backend. Investigating.
[-]Categories - Unable to disable Categories after changing category visibility settings[/-][+][Category Visibility] 1.b.3 [Ring1][Auth] Categories can't be turned off while a member's category visibility is restricted[/+]chiragsalian commentedon Nov 17, 2026
The fix for this is in Auth. The PR is merged. It should be deployed tomorrow and then i'll remove the blocker label on this.
If this is the last thing holding up deploy we can revert the beta PR i.e., this or disregard this blocker. I think the latter is fine because this is an edge case and not a common scenario and we have a fix that will go live soon.