Troubleshooting
| Result | Meaning | Action |
|---|---|---|
UNAUTHORIZED | Extension session or AI grant is invalid/expired | Sign in again or authorize that AI client |
ACCOUNT_MISMATCH | The token/returned identity does not match the selected account | Open the intended Ads API page and confirm its account |
SESSION_EXPIRED | Telegram rejected the saved provider credential | Explicitly transfer a replacement official API token |
MIGRATION_REQUIRED | The saved record used legacy cookies | Transfer an official API token; cookies are not reused |
CONNECTION_VERSION_CONFLICT | Credentials changed during the operation | Refresh metadata before retrying |
CONNECTION_DISCONNECTED | The locally stored provider token was removed | Create a new connection if access is still wanted |
UPSTREAM_UNAVAILABLE | Network or provider outage | Retry later; saved credentials remain intact |
RATE_LIMITED / BUSY | Provider quota or local concurrency limit reached | Reduce concurrent reads and retry later |
UNSUPPORTED_OPERATION | This read has no supported official-provider mapping | Use supported tools; preview availability is not moderation success |
PROTOCOL_DRIFT | Telegram returned an unexpected response | Report the error code; never attach tokens or raw private responses |
A saved active status is historical. Check verifies the connection now. If the popup closes or a status request fails, keep settings and retry. A revoked AI authorization does not delete the advertising connection, and an analytics API key does not replace Ads consent.
Do not paste Telegram tokens, extension access tokens, internal service keys or browser cookies into support messages. Public metadata and sanitized error codes are enough to start an investigation.