Hi all,
Posting this as a UX/technical bug report rather than an account-specific request, since the problem is that the reactivation flow itself appears broken and I’d like to know whether others have hit the same defect.
Reproduction:
- Loading chatgpt.com redirects to chatgpt.com/workspace/deactivated.
- That page renders completely blank — no text, no reactivation button, no payment form. Nothing.
- The documented self-service path (workspace switcher → ••• → Reactivate) never appears, and no “create a Personal workspace” prompt is shown either.
- The /admin/billing link redirects straight back to the same blank /workspace/deactivated page — an endless loop with no exit.
- Console shows {“code”:“deactivated_workspace”} and the backend endpoints the UI needs to render the reactivation/payment view (/backend-api/me, /backend-api/settings/user, /backend-api/accounts/check, checkout config, etc.) all return HTTP 402.
So the deactivation state seems to block the very endpoints required to display the reactivation UI, which makes self-service reactivation structurally impossible even for a workspace owner.
My questions to the community:
- Is this a known regression in the deactivated-workspace flow? There’s a prior report describing an identical blank /workspace/deactivated page with a DeactivatedWorkspaceModal render failure.
- For anyone who recovered from this state — did the reactivation UI eventually render again on its own, or did it strictly require manual intervention?
- Is there any supported client-side workaround to get the reactivation/payment view to render while in this 402-locked state?