---
title: "Coming back after cancelling"
description: "Reactivation buys back every priced Project at once, why a single Project cannot be reactivated on its own, and what happens if the set changes."
updated: "2026-08-28"
verifiedAgainst:
  - apps/web/lib/server/workspace-subscription-activation.ts
  - apps/web/app/api/billing/create-checkout/route.ts
  - apps/web/lib/server/site-tiers.ts
---

A cancelled workspace still holds everything it had. Reactivating is not buying a
Project again; it is restarting the subscription that covered all of them.

## The whole portfolio comes back together

When you reactivate, Blogged reads the Projects your workspace already owns,
prices each one at its own plan and its own discount position, and takes the
total as a single charge. Checkout shows one line, named for the number of
Projects it covers, and the subscription is rebuilt into one item per Project
after payment. The first invoice and every invoice after it come to the same
subtotal.

The set is fixed before Stripe collects anything, so the amount you are shown is
the amount for the exact Projects your workspace holds at that moment.

## You cannot reactivate one Project on its own

Selecting a single Project and asking to buy it at a different plan is refused.
The message names the plan that Project already carries and asks you to
reactivate the exact portfolio first.

<Callout variant="note" title="Why it works this way">
  Buying one Project alone would reopen the workspace's subscription while paying
  for a fraction of what it covers, and it would silently re-tier every other
  Project's discount position. Reactivate first, then change that Project's plan
  through the normal quoted flow, where you are shown what the change costs before
  you confirm it. See [changing a plan](/billing/change-plan).
</Callout>

## If the set changes while checkout is open

Reactivation is bound to the exact list of Projects it was priced against. If a
Project is archived, restored or moved to a different plan between opening
checkout and paying, the amount collected no longer describes what is being
delivered.

That case fails closed. Delivery stops rather than applying a different portfolio
than the one that was paid for, and after the retries are exhausted the new
subscription is cancelled and the charge refunded automatically. Access stays
closed the whole time. See
[when delivery cannot be completed](/billing/checkout).

The practical consequence is small: finish the reactivation before archiving or
re-tiering anything, and if you do change your mind mid checkout, let it fail and
start again rather than trying to force it through.

## What reactivation does not do

- It does not restore a spent Free grant. That benefit is used once, and
  cancelling never returns it. See [the Free grant](/billing/free-grant).
- It does not recreate anything. Posts, topics, knowledge and assets were never
  removed by the cancellation.
- It does not change any Project's plan. Each comes back on the plan it was on.

## If your blog stopped being served

A cancelled workspace stops serving its public blogs, and reactivating starts
that again. A custom domain that you removed or repointed at your DNS provider
after cancelling has to be pointed back. See
[custom domains](/blog/custom-domain).