Replacing Roles and Channels

A role, a channel or the server in Subscriby is a resource: something a plan grants. When a role is deleted, a channel is gone, the app is removed from a server, or the server itself is lost, the resource still exists, the plans still sell it, the members still hold it; only the place is gone. The Places recovery points the resource at a replacement and re-admits every member who holds it.

Discord cannot ban the Subscriby app the way Telegram bans a bot, so there is no app to replace and no standby app: the recovery is about places, and about your own account (Recovering your Discord account).

The pageCopy Anchor Link

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 (Discord no longer has this place, The app cannot see this place, The app lost Manage Roles, Drag the Subscriby role above …). 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 window is open or still to come.
• 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 app a new placeCopy Anchor Link

Create the replacement in Discord first, of the same kind: a role for a role, a channel for a channel. Then either:

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

The app refuses a place that is already a resource of any project, and a role that sits above its own role in the role list. A server that takes over from a lost one, like a standby server, is picked on the dashboard: Discord has no menu for servers in a reply.

What happens in the swapCopy Anchor Link

In one transaction the resource is re-pointed at the new place, switched on and marked healthy. Then, from the queue, every member with active access to the resource is re-admitted through the usual doors:

1. A member in the server is given the new role at once (for a channel, the role the app makes for it).
2. A member who connected Discord on the portal is added to a replacement server by the app itself, with the role.
3. Everyone else receives a single-use invite to the new place, on the portal, in a direct message when the app can reach them, and in /subscriby status; their access completes the moment they join.
4. The old place is left exactly as it is, nobody is removed from it, and project.resource.updated fires with changes.space_id; the open incident resolves.

The roll call counts a direct add or a role as re-admitted and an invite as invited, not yet in, so it never counts a member back in before they are.

Members the app cannot reachCopy Anchor Link

A member who never connected Discord and whose direct messages are closed to the app still holds their invite on the portal, but is not told. The step lets you choose:

• Email them for me — Subscriby emails each unreachable member who has an email address, verified on the portal or used to pay, their new link, at $0.01 per email, added to your transaction fees. Members the app 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 callCopy Anchor Link

Below the table, the roll call follows the queue: Re-admitted x / total (members holding the new role or a new invite), Joined (members who came through), Could not be messaged and Told by email. Remind Members Still Outside re-sends the invite message to everyone who has not joined yet, in their direct messages only; it can be pressed once per hour.

Standbys, the mirror and automatic failoverCopy Anchor Link

On Growth, each place can have one standby of the same kind, picked on the Prevention page or with /subscriby-admin recovery standby <place>; a standby server is picked on the Prevention page only. The app already administers the standby, so it is probed alongside the resource and a swap needs no round trip.

For a channel, the mirror copies every post into the standby channel the moment it is made, replaces the copy when the post is edited and removes it when the post is deleted, attachments included up to Discord's upload limit. /subscriby-admin recovery standby <place> mirror:True links a standby and switches the mirror on in one go. Posts made before the mirror was switched on are not copied; switch it on early.

With Automatic Failover on, a place Discord no longer has, or an app removed from its server, is swapped for its healthy standby the moment the probe finds it, with nobody signed in, and the roll call runs as above. The readiness checklist's Discord lines, A Standby for Every Place, Automatic Failover, Live Mirror of Your Channels and Connect Discord for Every Member, show where you stand; /subscriby-admin recovery status prints the same lines in the server.

Several places at onceCopy Anchor Link

A places recovery absorbs every further swap you make within 24 hours of the first: three lost channels 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.

UndoCopy Anchor Link

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 invites into the replacement are withdrawn, and everyone is re-admitted to the old place through the same queue. No allowance is spent by an undo.

Example: a channel deleted by a moderatorCopy Anchor Link

A trading educator sells a Signals channel and a VIP role through one plan. At 21:40 a moderator deletes the channel by mistake; the role is fine.

• The five-minute pass-window probe (a weekend pass is open) finds Discord no longer has this place and opens the incident; email and a Discord alert at 21:41.
• The educator had linked a standby channel with the mirror on, so Use Standby is on the row: one press at 21:47 and the resource points at the standby, which already holds every post since the mirror was switched on.
• 212 members hold live access; all are in the server, so within a minute the roll call reads Re-admitted 212 / 212 · Joined 212: a role is given, not an invite clicked.
• They link a fresh standby for next time and switch the mirror on for it. The Places allowance is spent until 90 days later; a second loss before then goes through support.

RelatedCopy Anchor Link

• Replacing a lost place — the connector-neutral page.
• Active Disaster Prevention — standbys, the mirror and automatic failover.
• Admin commands — /subscriby-admin recovery in the server.