How the App Stays Connected

You don't need to configure anything for the Subscriby app to stay connected to Discord: everything is handled on our side once you add the app to a server. This page explains how it works, for curiosity's sake and for troubleshooting if the app ever goes quiet.

The short versionCopy Anchor Link

Discord does not call Subscriby when something happens in your server. Instead, Subscriby keeps a live connection open to Discord, the same kind every Discord app uses, and Discord streams events down it as they happen: a member joined, a slash command was run, a message was posted in a mirrored channel. Subscriby answers over Discord's API within a second or two.

That's the whole story. No webhook to register, no polling, no server of yours in between.

What Subscriby does automaticallyCopy Anchor Link

• Keeps the connection up. A worker holds the connection open around the clock and resumes it after a hiccup, picking up the events it missed meanwhile.
• Answers every command inside Discord's three seconds. A slash command is acknowledged at once and the answer follows, which is why a reply sometimes reads thinking for a moment.
• Reconciles every fifteen minutes. The server's roles are compared with the membership ledger and any drift is repaired, so an event the connection missed never costs a member their access for long.
• Probes every hour. The hourly health check asks Discord about the server and the app's role, and Run Doctor on the Connectors page asks about every place you sell on demand.
• Registers the commands once. /subscriby and /subscriby-admin are registered globally with Discord on every release that changes them; a new command can take up to an hour to appear in every server, which is Discord's own propagation time.

What you don't need to configureCopy Anchor Link

• A bot or a token — Subscriby's own verified app serves every server.
• An interactions endpoint or a webhook — the live connection carries everything.
• A server of your own — Subscriby runs the worker.
• Intents or privileges — the app's permissions in your server are the whole configuration, and they are set when you add it.

When this matters for youCopy Anchor Link

Ninety-nine percent of the time you'll forget any of this exists. The moments you might care:

The app stops respondingCopy Anchor Link

If /subscriby-admin or /subscriby returns nothing, or roles stop appearing, check the Connectors page first. Its health states name the cause:

• App removed — the app was removed from the server, or the server is gone. Add it back with Reconnect; members keep their memberships and are given their roles again.
• Permissions trimmed — someone edited the app's role in Server Settings. Give it back Manage Roles, Manage Channels, Create Invite and Kick Members, and drag it above the roles you sell.
• Token refused — Discord refused the app itself. Nothing on your side changed; this is Subscriby's to fix.
• Discord unreachable — Discord could not be reached or answered with an error. This usually clears on its own; the next check will tell.

If the state is Connected and a command still returns nothing, Discord may be propagating a new command set, or the member is running /subscriby in a server the app is not connected to a project in. Run Doctor lists every place with the fix beside it.

A role is missing or lingeringCopy Anchor Link

A member who should have a role and does not, or who lost access and still carries one, is repaired by the fifteen-minute reconciliation on its own. To fix it now, the member can run /subscriby refresh, or you can Suspend and Restore their access from the Members page.

The commands do not appear in DiscordCopy Anchor Link

Commands are registered globally and Discord propagates them within an hour. A server where the command is hidden for someone checks their Discord permissions: /subscriby-admin is visible only to members with Manage Server, and a server's own Integrations → Subscriby page can restrict either command further.

Subscriby pauses the connectorCopy Anchor Link

During an incident on Discord's side or ours, Subscriby can switch the whole connector off for a while. The Connectors page shows the row as Paused, a slash command answers that Subscriby is paused on Discord for a moment, and nothing is sent, probed or changed; what members do in the meantime waits on Discord and is picked up when the connector is switched back on. Your installations, plans and members are untouched.

Security notesCopy Anchor Link

• Every event Subscriby acts on arrives over its own authenticated connection to Discord; nothing reaches Subscriby from a third party pretending to be Discord.
• The app reads messages in three places only: channels you mirror into a standby, the support threads it opened, and the direct messages people send it. Everything else in your server is never read.
• Members who connect their Discord account on the portal authorise three things, to read their profile, to be added to your server, and to carry their membership badge for Linked Roles; the authorisation is stored encrypted and renewed daily, and can be withdrawn by the member from Discord's own authorised-apps settings at any time.

RelatedCopy Anchor Link

• Connect a Discord server — the permissions, the role to drag, and the health states.
• Integration — the higher-level mechanics (member add/remove, etc.).
• Troubleshooting — common cross-cutting issues.