Registration troubleshooting
Diagnose callback, account-selection and duplicate-Page failures.
Provider returns to the landing page
Return to Register Page or Console → Pages and start the provider step again. If it returns to the landing page a second time, contact support with the provider, UTC time and the page where you started. Do not share the authorization URL.
Account already linked
Connection ownership is exclusive. Choose a different provider account, or sign out intentionally and use the Clawdbase account that already owns that identity. The current session should remain unchanged after this error.
The same Page appears twice
Reload Pages once. If the same provider asset still appears twice, contact support with both public Page links. Do not decide which record is correct from the handle or score alone.
X says the app cannot be authorized
Start again from Clawdbase rather than reusing the failed X URL. If X still rejects access, provide support with the time and error text, but not the full authorization URL.
GitHub rejects the callback
Start again from the GitHub option. If GitHub still rejects the callback, provide support with the displayed message and time. Do not edit the URL or attempt to select a repository by typing it into Clawdbase.
Telegram says redirect_uri required
Start again from the Telegram option. If Telegram still reports a redirect error, provide support with the displayed message and time; do not send the full OAuth URL or code.
Diagnose in order
Identify the failed boundary
Note whether the error appeared before provider consent, after returning to Clawdbase, while selecting an asset, or while scoring.
Preserve correlation data
Record provider, initiating page, UTC timestamp and the safe error code shown. Never share authorization codes, tokens, cookies or complete authorization URLs.
Verify return behavior
Confirm you returned to Register Page or the initiating Console tab. If you landed elsewhere, include that destination in the support report.
Retry from start
Begin a new authorization from Clawdbase. Never replay or bookmark a provider callback URL.
Account already linked
This conflict means the provider account is already owned by another Clawdbase user. The current account remains signed in and no new Page is created. Choose another provider account or sign out intentionally.
Same Page appears twice
Contact support with both public Page links. Handles can change, so Clawdbase reconciles the records from immutable provider identity rather than simply hiding one matching label.
Same account keeps being selected
Clawdbase cannot choose a provider account by accepting a typed handle. Start a new provider authorization and let the provider present its account-selection or session controls. Reauthorizing the same immutable ID must return matched, not create another Page.
Scoring remains pending
Registration can succeed before initial scoring completes. Open the Page and use Retry if the state changes to unavailable. Do not create the Page again as a scoring retry.
Support checklist
Include the provider, initiating page, approximate UTC time, public Page link if created, and safe error code. Exclude secrets, cookies, OAuth codes, access tokens and payment details.