Ctrlk
Start NowBlogsWatch NowContact Us
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Scanning & Upload - Analysis doesn't start after upload

Symptoms

  • You uploaded a SAST report (and/or source code) but the analysis phase never begins.

  • The report appears stuck, or you're told there are no fixes even though the analysis didn't run.

Likely cause

The fix-report submission was incomplete — for example, the source code wasn't provided or matched to the report, so the analysis phase was never initiated.

Resolution

  1. Restart the flow and make sure you complete every step of "Fix my code": provide the SAST report and the corresponding source code when prompted.

  2. Confirm the source code matches the codebase the report was generated from.

  3. If it still doesn't start, retry the submission using the Mobb CLI with debug enabled to capture verbose output, and share it with support@mobb.ai.

Still stuck? Contact support@mobb.ai.

PreviousSCM Connection - Azure DevOps OAuth won't completeNextScanning & Upload - Large report file won't upload

Last updated