Replacing a Lost Place

When the platform bans a place your plans grant, or the connector loses the rights to run it, hand the connector a replacement, watch every member be re-admitted, remind the ones still outside, choose how unreachable members are told, and undo within 24 hours.

A place in Subscriby is a resource: something a plan grants. When the platform bans the place behind it, or the connector loses the rights it needs there, the resource still exists, the plans still sell it, the members still hold it; only the place is gone. The place recovery points the resource at a replacement and re-admits everyone who is entitled to be there.

Content does not come back

Once a platform bans a place, nothing can read its history back, ours included. Recovery brings back the members, not the posts. On Growth, the live mirror copies every post into your standby place as you publish it, so a failover lands members somewhere that already holds your content. That is the only content safeguard there is; the readiness checklist reminds you to keep a copy outside the platform too.

The page

Choose the project (if you own several) and the step lists every place of the project with:

  • Health: the last probe's verdict, Healthy or the reason it is degraded, in the connector's own words. A resource switched off shows Switched Off; one already swapped in this recovery shows Replaced.
  • Plans: how many plans grant it.
  • Members Affected: how many members the swap moves. Everyone with active access, plus every pass and season-ticket holder whose date is open or still to come. Those inside an open window are re-admitted at once; the rest receive their access to the new place before their date opens, and it waits until the window opens, exactly as it would have in the original place.
  • Standby: on Growth, the standby place linked to it and whether it is healthy.

At the top, a badge says where your allowance stands: 1 self-service recovery available, Recovery in progress — further swaps join it, or Used on date — contact support with a Contact Support button that opens the chat with the incident already attached.

Handing the connector a new place

Create the replacement on the platform first, of the same kind as the one it replaces; the connector says which kinds may stand in for which. Then:

Press Replace

The connector asks you, on the platform, to pick the new place, and takes the rights it needs there through that pick.

Or give it the rights yourself

Make the connector's installation an administrator of the new place with the rights the connector names. The moment that happens while a replacement is waiting, it asks whether the new place should replace the lost one.

Watch the page

The row showed Waiting on the connector (with a Withdraw Request button in case you change your mind); it now shows Replaced, an Undo button, and the roll call starts filling below the table.

On Growth with a healthy standby linked to the resource, the row also has Use Standby: one click, no round trip to the platform, and the standby becomes the resource's place.

The connector refuses a place that is already a resource of any project, and refuses a place of the wrong kind.

What happens in the swap

In one transaction the resource is re-pointed at the new place, switched on, marked healthy, and the access minted into the old place is forgotten. Then, from the queue:

  1. Every member with active access to the resource, through a live subscription or through a pass or pass-series date whose window is open right now, gets fresh personal access into the new place. Holders whose window is still ahead have their old access forgotten and are picked up by the ordinary pre-window sweep, so they are not messaged twice; see pass and pass-series holders.
  2. Each member is told by the project's bot that the place has moved, with a button to join. The connector admits them when they use it.
  3. The old place is left exactly as it is, nobody is evicted, and the access into it is revoked, best-effort.
  4. project.resource.updated fires with changes.space_id, and the open incident resolves.

Members the bot cannot reach

Some members never opened your project's bot (they bought through the portal), and if the bot was banned in the same incident it cannot message anyone at all. Those members still hold their new access, which appears in the portal and the moment they open the bot, but they are not told. The step lets you choose, per project, how they are reached; the choice is remembered:

  • Email them for me. Subscriby emails each unreachable member who has an email address, verified on the portal or used to pay, their new access, at $0.01 per email, added to your transaction fees. Members the bot could reach cost nothing.
  • I will email them myself. Nobody is emailed. Press Download Member List (CSV) for every member the swap moves, with the email they verified or paid with if any, and reach them your own way.

The re-admission roll call

Below the table, the roll call follows the queue: Re-admitted x / total (members holding new access), Joined (members who actually came through it, stamped the moment the connector admits them), Could not be messaged and Told by email. A badge summarises it: n still to join, or Everyone Has Joined.

Remind Members Still Outside re-sends the "has moved" message, with the same access, to everyone who has not joined yet, in the connector's chat only; nothing is minted or emailed again. It can be pressed once per hour, through the same rate-limited queue as the swap, so a place's worth of people is never messaged twice in a minute. The same button sits on the history row.

Several places at once

A place recovery absorbs every further swap you make within 24 hours of the first: three banned places fixed in one sitting are one use of the allowance, not three, and the page says Recovery in progress — further swaps join it. The roll call covers all of them together.

Undo

Each swap can be undone for 24 hours from the Undo button on its row, or from the history page. The resource goes back to its previous place, the access into the replacement is forgotten, and everyone is re-admitted to the old place through the same queue. No allowance is spent by an undo.

Per connector

On Telegram a place is a channel, group or supergroup, the pick happens through a chat-picker button our platform bot sends you, the rights are invite users and restrict members for @SubscribyBot, a group may be replaced by a supergroup but a channel never by a group, and the access is a personal invite link whose join request is approved automatically. The Telegram walkthrough with a two-channel example is on Replacing channels and groups.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request