Browse documentation
bbradar Pro guide
Troubleshoot Pro setup
Resolve common Telegram rule, opportunity-filter, Discord, MCP, API, billing, target-feed, and repository issues.
8 min read
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 and Telegram, not the current API or MCP tools.
Telegram issues
- Symptom
- I cannot find the bot
- Likely cause
- Telegram search can show similar display names.
- Fix
- Open the verified @bbradario_bot link and confirm the exact username.
- Symptom
- Pressing Start only shows setup help
- Likely cause
- The bot was opened without the account-generated token.
- Fix
- Return to Account & Billing and select Connect Telegram so bbradar opens the tokenized link.
- Symptom
- Start link says it is invalid or does nothing
- Likely cause
- The single-use token expired or a newer link replaced it.
- Fix
- Return to Account & Billing, select Connect Telegram or Reconnect, and use the newest link within about 10 minutes.
- Symptom
- Status remains Not connected
- Likely cause
- Start was not pressed on the tokenized link, or the account page has not refreshed.
- Fix
- Press START in the @bbradario_bot private chat, wait for Telegram connected, return, and select Refresh.
- Symptom
- Status is Blocked
- Likely cause
- The official bot was blocked or Telegram rejected delivery.
- Fix
- Unblock @bbradario_bot, then create and consume a new connection link.
- Symptom
- Telegram account is already linked
- Likely cause
- That Telegram account belongs to another bbradar user.
- Fix
- Disconnect it from the other account or contact support.
- Symptom
- Connected but no alerts arrive
- Likely cause
- Pro is inactive, streams are off, or filtered mode does not match.
- Fix
- Confirm Pro, integration status, enabled streams, filters, Telegram DM delivery, and that you selected Save Rules.
- Symptom
- Opportunity-filtered alerts disappeared
- Likely cause
- The event lacks a selected tier, score, label, or dupe-risk value, or it fails another active filter group.
- Fix
- Clear the signal group back to All or Any, or broaden the selections. Remember that Unknown is separate from Low dupe risk.
| Symptom | Likely cause | Fix |
|---|---|---|
| I cannot find the bot | Telegram search can show similar display names. | Open the verified @bbradario_bot link 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. |
Discord issues
- Symptom
- OAuth completes but no role appears
- Fix
- Join the bbradar Discord with the linked account, then select Reconnect Discord.
- Symptom
- Wrong Discord account is linked
- Fix
- Select Connect a different Discord account and authorize the intended identity, or contact support if it cannot be replaced.
- Symptom
- Role disappeared
- Fix
- Confirm Pro is still active; role reconciliation removes access after Pro expires.
| 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; role reconciliation removes access after Pro expires. |
API and MCP issues
- Symptom
- MCP server will not start
- Fix
- Confirm Node.js 20+, run npx -y @bbradar/mcp once in a terminal, and use the Windows cmd /c fallback if needed.
- Symptom
- get_mcp_status reports unauthorized
- Fix
- Check BBRADAR_API_KEY, ensure the key was not regenerated or deleted, and confirm Pro is active.
- Symptom
- API returns 401
- Fix
- Send the current full secret as an Authorization: Bearer header.
- Symptom
- API returns 402
- Fix
- Restore active Pro access.
- Symptom
- API returns 423
- Fix
- Stop traffic and wait for the abuse-protection lock to expire.
- Symptom
- API returns 429
- Fix
- Reduce request rate and concurrency, then retry with exponential backoff and jitter.
| 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 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. |
Feed and repository issues
- Symptom
- A visible upstream edit is absent
- Explanation
- The transition may be non-material, unconfirmed, a backfill, normalization-only, or protected by partial-snapshot safety.
- Symptom
- A new repository has no event
- Explanation
- The first successful branch observation is a silent baseline.
- Symptom
- Commits did not update immediately
- Explanation
- The browser refreshes about once per minute only while the Commits view is active and visible.
- Symptom
- A GitLab or Bitbucket target has no commits
- Explanation
- Current ref monitoring is implemented for GitHub only.
- Symptom
- A tag or pinned SHA does not change
- Explanation
- Immutable selectors are mapped but not polled.
| Symptom | Explanation |
|---|---|
| A visible upstream edit is absent | The transition may be non-material, unconfirmed, a backfill, normalization-only, or protected by partial-snapshot safety. |
| A new repository has no event | The first successful branch observation is a silent baseline. |
| Commits did not update immediately | The browser refreshes about once per minute only while the Commits view is active and visible. |
| A GitLab or Bitbucket target has no commits | Current ref monitoring is implemented for GitHub only. |
| A tag or pinned SHA does not change | Immutable selectors are mapped but not polled. |
Still stuck?
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.