Troubleshoot social authorization
Popup settings, correct platform account, eligible assets, scopes, token expiry, cancel state, and reconnecting. Core.
Overview
Popup settings, correct platform account, eligible assets, scopes, token expiry, cancel state, and reconnecting. Core. Use this guide to isolate the cause safely before repeating the action. Security and troubleshooting depend on precise timestamps, states, permissions, service health, and reproducible steps.
Identify the symptom
Popup settings, correct platform account, eligible assets, scopes, token expiry, cancel state, and reconnecting. Core. Note the exact point where the actual behavior differs from what you expected.
Do not repeatedly submit, delete, publish, reconnect, or purchase while the result is uncertain. First verify whether the previous action completed in another tab, activity list, Audit Log, or external platform.
Checks to make in order
Start in Audit Log, System Status, or the affected feature. Keep the affected item open where possible so you can compare the state after each check.
- Check 1: Popup settings
Review popup settings and choose the value that matches your intended result.
- Check 2: Correct platform account
Review correct platform account and choose the value that matches your intended result.
- Check 3: Eligible assets
Review eligible assets and choose the value that matches your intended result.
- Check 4: Scopes
Review scopes and choose the value that matches your intended result.
- Check 5: Token expiry
Review token expiry and choose the value that matches your intended result.
- Check 6: Cancel state
Review cancel state and choose the value that matches your intended result.
- Check 7: Reconnecting
Review reconnecting and choose the value that matches your intended result.
Safe recovery
After correcting the cause, refresh the page and repeat the smallest safe action that can prove the workflow works. The issue is resolved when the cause is identified, the safe recovery action is complete, or support has enough context to investigate.
If a retry could publish, delete, charge, revoke access, retire a public address, or send a message twice, contact an owner or support instead of guessing.
- Record the organization, route, item ID, time and timezone, exact message, and steps that reproduce the issue.
- Check System Status and Audit Log before repeating a destructive or security-sensitive action.
- Never send passwords, verification codes, cookies, access tokens, API keys, or other secrets.
If you still need help
Send support the organization name, route, affected item ID, timestamp and timezone, exact message, screenshot, and reproducible steps. Include the relevant System Status or Audit Log entry when available.
Never send passwords, verification codes, cookies, access tokens, API keys, payment details, or other secrets.
Availability and access
This feature does not require an add-on, although permissions or organization settings may still apply.