> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/scanning/scanning-ci-cd-pipelines/understanding-pipeline-scan-results/pipeline-issues.md).

# Pipeline Issues

The Pipeline Issues page presents all the issues found during pipeline scans. You can configure [pipeline workflows](/automate-with-ox-workflows/pipeline-workflows.md) to react differently to new vs. old issues.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-83e9cf9b8f0e2acf31855287ec83d1de55c4d773%2FPipeline_Issues1.png?alt=media" alt=""><figcaption></figcaption></figure>

Pipeline issues include an additional status field that does not exist in the Active Issues page:

* **New**: Issue did not appear in previous scans.
* **Old**: Issue already exists in the Active Issues page.

### Understanding Pipeline Issue Results

Pipeline issues can have one of the following results:

<table><thead><tr><th width="124.83331298828125">Result</th><th>Description</th></tr></thead><tbody><tr><td>Discovered</td><td>The issue was detected during the pipeline scan. All newly detected pipeline issues start in this state.</td></tr><tr><td>Monitored</td><td>The issue matched a workflow that contains an Alert action. The issue is reported and tracked but does not block the pipeline.</td></tr><tr><td>Blocked</td><td>The issue matched a workflow that contains a Block action. The issue contributes to blocking the pipeline according to the configured workflow.</td></tr></tbody></table>

The results shown on this page contribute to the overall pipeline scan result displayed on the [Pipeline Summary](/ox-code/scanning/scanning-ci-cd-pipelines/understanding-pipeline-scan-results/pipeline-summary.md) page.

* If one or more issues are Blocked, the pipeline result is Blocked.
* If no issues are blocked but one or more issues are Monitored, the pipeline result is Monitor.
* If no issues are monitored or blocked, the pipeline result is Passed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/ox-code/scanning/scanning-ci-cd-pipelines/understanding-pipeline-scan-results/pipeline-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.