# Troubleshoot Pro setup | bbradar.io

> Resolve common Telegram rule, opportunity-filter, Discord, MCP, API, billing, program History, target-feed and repository issues.

Source: [https://bbradar.io/docs/troubleshooting](https://bbradar.io/docs/troubleshooting)

<a id="quick-checks"></a>

## [Quick checks](https://bbradar.io/docs/troubleshooting.md#quick-checks)

1. ### Confirm Pro is active

   Open Account & Billing and verify the subscription status before debugging an integration.
2. ### Refresh once

   Reload the account page or use the integration Refresh action after completing an external flow.
3. ### Use the newest credential

   Old Telegram links and regenerated API keys stop working immediately.
4. ### Check the exact feature boundary

   Repository changes are in the Commits feed, the read-only Pro API, supported notifications, and get_repository_changes in MCP 0.2.3. Self-Hosted repository monitoring remains unavailable.

<a id="telegram-issues"></a>

## [Telegram issues](https://bbradar.io/docs/troubleshooting.md#telegram-issues)

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| I cannot find the bot | Telegram search can show similar display names. | Open the verified [@bbradario_bot link](https://t.me/bbradario_bot) and confirm the exact username. |
| Pressing Start only shows setup help | The bot was opened without the account-generated token. | Return to Account & Billing and select Connect Telegram so bbradar opens the tokenized link. |
| Start link says it is invalid or does nothing | The single-use token expired or a newer link replaced it. | Return to Account & Billing, select Connect Telegram or Reconnect, and use the newest link within about 10 minutes. |
| Status remains Not connected | Start was not pressed on the tokenized link, or the account page has not refreshed. | Press START in the @bbradario_bot private chat, wait for Telegram connected, return, and select Refresh. |
| Status is Blocked | The official bot was blocked or Telegram rejected delivery. | Unblock @bbradario_bot, then create and consume a new connection link. |
| Telegram account is already linked | That Telegram account belongs to another bbradar user. | Disconnect it from the other account or contact support. |
| Connected but no alerts arrive | Pro is inactive, streams are off, or filtered mode does not match. | Confirm Pro, integration status, enabled streams, filters, Telegram DM delivery, and that you selected Save Rules. |
| Opportunity-filtered alerts disappeared | The event lacks a selected tier, score, label, or dupe-risk value, or it fails another active filter group. | Clear the signal group back to All or Any, or broaden the selections. Remember that Unknown is separate from Low dupe risk. |

<a id="discord-issues"></a>

## [Discord issues](https://bbradar.io/docs/troubleshooting.md#discord-issues)

| Symptom | Fix |
| --- | --- |
| OAuth completes but no role appears | Join the bbradar Discord with the linked account, then select Reconnect Discord. |
| Wrong Discord account is linked | Select Connect a different Discord account and authorize the intended identity, or contact support if it cannot be replaced. |
| Role disappeared | Confirm Pro is still active; the Discord Pro role can be removed after Pro expires. |

<a id="api-mcp-issues"></a>

## [API and MCP issues](https://bbradar.io/docs/troubleshooting.md#api-mcp-issues)

| Symptom | Fix |
| --- | --- |
| MCP server will not start | Confirm Node.js 20+, run npx -y @bbradar/mcp once in a terminal, and use the Windows cmd /c fallback if needed. |
| get_mcp_status reports unauthorized | Check BBRADAR_API_KEY, ensure the key was not regenerated or deleted, and confirm Pro is active. |
| API returns 401 | Send the current full secret as an Authorization: Bearer header. |
| API returns 402 | Restore active Pro access. |
| API returns 410 | The snapshot or retained cursor expired. Restart a snapshot on page 1 or reconcile the current inventory before resuming change polling. |
| API returns 413 | Narrow the filters or page size. Snapshot results and repository associations have explicit size limits. |
| API returns 423 | Stop traffic and wait for the abuse-protection lock to expire. |
| API returns 429 | Reduce request rate and concurrency, then retry with exponential backoff and jitter. |
| API returns 503 | A required service is temporarily unavailable. Honor Retry-After when present and retry with bounded backoff. |

<a id="feed-issues"></a>

## [Feed and repository issues](https://bbradar.io/docs/troubleshooting.md#feed-issues)

| Symptom | Explanation |
| --- | --- |
| A visible upstream edit is absent | Latest Targets shows confirmed, meaningful changes. Wait for the next refresh and check the official source directly. |
| A program’s History tab is empty | Choose All events and a broader date range. Initial observations establish a silent starting point, and section coverage varies by provider. |
| History access changed | Confirm that you are signed in with active Pro access, then use the displayed account refresh or retry action. |
| A new repository has no event | The first observation establishes a starting point; later branch changes can appear as events. |
| Commits did not update immediately | The browser refreshes about once per minute only while the Commits view is active and visible. |
| A supported repository target has no commits | Confirm that the target links to a supported, accessible repository and branch. Private or self-managed repositories may not have coverage. |
| A tag or pinned SHA does not change | Tags and pinned commits are fixed references, so they do not produce later branch-change events. |

[Check History coverageUnderstand silent starting points, detection times and missing changes.](https://bbradar.io/docs/pro/program-history.md#missing-changes)

<a id="contact"></a>

## [Still stuck?](https://bbradar.io/docs/troubleshooting.md#contact)

Collect the page URL, approximate time, visible status or HTTP code, browser/OS, and a short description of what you expected. Do not include secrets, session cookies, Telegram start links, OAuth callbacks, or payment details.

[Contact account or billing supportEmail info@bbradar.io for private account, access, or billing questions.](mailto:info@bbradar.io)[Ask in the bbradar DiscordShare the non-sensitive context needed to reproduce the issue.](https://discord.gg/4DAm4Gg8JC)[Read the product FAQCheck product access, data, billing, and monitoring boundaries.](https://bbradar.io/docs/faq.md)