> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/snyk-ci-cd-integration-deployment-and-strategies/ci-cd-troubleshooting-and-resources.md).

# CI/CD troubleshooting and resources

This page provides a few tips to help troubleshoot or scale CI/CD integrations.

### Step 1: Try to replicate with the Snyk CLI

If the CLI and the pipeline are running the same engine, try to clone the Project and scan with the CLI.

Try various CLI options. Use the Snyk CLI to find and fix known vulnerabilities as you run it in the pipeline. For more information, see the [CLI documentation](/developer-tools/snyk-cli/snyk-cli.md).

### Step 2: Get logs

If you can replicate the issue using the Command Line Interface (CLI) and the problem still exists, consult the [Debugging the Snyk CLI ](/developer-tools/snyk-cli/snyk-cli/debugging-the-snyk-cli.md)troubleshooting guidelines for capturing logs in a debug mode.

### Step 3: Use the CLI instead of the plugin

Try to replace the native plugin with the CLI by installing the CLI. See [Install the Snyk CLI ](/developer-tools/snyk-cli/snyk-cli/install-the-snyk-cli.md)for instructions.

{% hint style="info" %}
The following repository provides some examples of binary and npm integrations for various CI/CD tools: [GitHub CI/CD examples](https://github.com/snyk-labs/snyk-cicd-integration-examples).

To learn more about CI/CD, see the article [What is CI/CD? CI/CD Pipeline and Tools Explained](https://snyk.io/learn/what-is-ci-cd-pipeline-and-tools-explained/).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/snyk-ci-cd-integration-deployment-and-strategies/ci-cd-troubleshooting-and-resources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.