Common Troubleshooting Scenarios

Solutions to the most common issues encountered when connecting, scanning, and fixing with Mobb. Each scenario is its own page — find your symptom, understand the likely cause, and follow the resoluti

This is a searchable knowledge base of the issues customers run into most often. Each scenario has its own page, written as Symptom → Likely cause → Resolution. Use the docs search bar (or your browser's find) to jump to your error message or symptom.

If you can't find your issue here, or a resolution doesn't work, contact us at [e-mail].

Broker & Tokens

• Expired broker token

• Rotated token but still failing

• Broker can't reach the SCM

• SCM or broker URL changed

SCM Connection

• Authorization error on connect

• Missing repositories after connecting

• No on-prem PAT connect option

• "Could not connect to the server"

• Azure DevOps OAuth won't complete

Scanning & Upload

• Analysis doesn't start after upload

• Large report file won't upload

• Upload fails due to file name

• Scan or analysis times out

• Mobb says my report is invalid

No Fix Available

• Supported issue shows no fix

• Finding marked irrelevant / false positive

• Zero fixes for the whole report

Reports & Findings

• Severities or counts differ from my scanner

Pull Requests

• PR creation fails

• PR stuck "In progress"

• Auto-PR isn't creating pull requests

• Azure DevOps rejects a PR with a long description

Mobb CLI

• Install blocked by npm registry

• Blocked by corporate proxy

• A CLI option isn't working as expected

Access & Onboarding

• Can't see any projects

• Getting an API key

• Using a shared/service account

• Setting up single sign-on (SSO)

Related guides

• Mobb Broker and Update Broker Token

• Mobb CLI Troubleshooting Guide

• Integrating SAST Findings

• Frequently Asked Questions (FAQ)