> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/troubleshooting/checkpoint-and-discord.md).

# Checkpoint and Discord problems

## Provider missing from the key page

Check its saved readiness: credential, link, return anchor, valid package, and enabled state. The package checkpoint count must fit the project limit. A configured token doesn't guarantee a usable package or a successful provider round-trip.

## Returned but no progress

Keep the original browser session. Start/resume from the actual project flow. Temporary callback destinations are single-use/session-bound; old tabs, another browser, cancelled runs and expired attempts can't complete the current step.

If the page reports captcha failure or TURNSTILE\_FAILED, complete a fresh verification. Don't reuse a consumed token. Provider outages and malformed return data can also reject progress; note which provider failed.

## Stacking blocked

STACK\_BLOCKED means the key lacks a usable original package or isn't checkpoint-issued stock. STACK\_COOLDOWN means wait the returned retry\_after seconds. Expired keys use renewal; lifetime/banned/revoked keys can't stack. Finish a pending flow or Discord claim before starting another.

## Discord connection won't finish

Match the application's redirect URI to the one displayed in the project. For auto-join, the application ID and bot token must belong together and the bot must already be in the selected server. Use the original flow browser and approve the requested permissions. A failed join leaves the claim incomplete.

## Panel says unavailable

Check View Channel, Send Messages and Read Message History. For roles, also check Manage Roles and hierarchy. Use /panel → Refresh / repair for a deleted message, or Move to channel for a deleted source channel. Select a connected loader if the previous one was removed.

Private panel menus expire after five minutes or a bot restart. Run /panel again. Published panels and saved keys remain. Owners need current project ownership for member management; Manage Server by itself isn't enough.

## Get Script has the wrong or missing loader

Each panel stores one stable loader selection. URL rotation is automatic, but deletion/disconnection is not. Change the selected loader explicitly in the panel settings. Saved keys remain project-scoped.

## When you ask for help

Include the visible code/message, provider or panel name, approximate time, and steps that led to it. For API calls include X-Request-Id. Don't post keys, provider tokens, bot tokens, auth secrets, or callback tokens in public chat.