Troubleshooting

Start with the pipeline log. The step names the scanner or the error.

Symptom	Cause and fix
The step fails naming a scanner	The scanner is missing from `PATH`, crashed, exited with an error or wrote no usable SARIF. Install it on the agent and rerun.
Ingest answers 401	The ingest token is missing, wrong or revoked. Mint a new one on the Pipeline page.
Ingest answers 415	Send `Content-Type: application/json`.
Ingest answers 400 `empty_sarif` or `invalid_sarif`	The body holds no SARIF, or documents that do not name their tool. Check the scanner output.
Ingest answers 409	The gate blocked the run. Open Findings, fix or except the findings at or above your threshold.
No comment on the pull request	Azure DevOps: add the `SYSTEM_ACCESSTOKEN` env line, give the build service Contribute to pull requests and run the pipeline on pull requests. GitHub: give the job `pull-requests: write`, and run on branches, not forks.
A change is refused with `insufficient_role`	Only workspace owners and admins can change the gate, tokens, the Azure DevOps share and exceptions.
No Marketplace link on the Pipeline page	The extension is shared by hand after you save your organisation. Until then, use the first-scan example or the GitHub Action.
Nothing under Findings	Send the first-scan example from the Pipeline page, then check the status filter on Findings.

For anything else write to hello@spot-suite.com and include the workspace address and the pipeline log.