> For the complete documentation index, see [llms.txt](https://www.quillaudits.com/quillshield/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.quillaudits.com/quillshield/help-center/integrations/why-isnt-my-integration-working.md).

# Why isn't my integration working?

Common GitHub, GitLab, CI, and MCP failures.

| Symptom                               | What to do                                                                                                                                                                                          |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| GitHub or GitLab connect fails        | Retry **Settings → Integrations**. Complete the OAuth popup. For GitHub automation, install the GitHub App from CI/CD Setup (user authorization during install is required). GitLab.com has no App. |
| Continue with GitLab is missing       | GitLab sign-in is not enabled for this environment. Email, Google, and GitHub sign-in are unchanged when they are enabled.                                                                          |
| CI scan HTTP 409                      | No completed full audit (+ graph) that is an ancestor of the scan target on the CI branch. Full-audit that history first.                                                                           |
| Full audit recommended                | The change adds new `.sol` files, ΔSLOC > 150, or > 5 changed Solidity files. The light scan still ran. Run a full audit for a new baseline.                                                        |
| Actions 402                           | Free light scans used up; top up the org owner wallet.                                                                                                                                              |
| MCP `wallet_topup_required`           | Top up at `/topup`, then retry with `confirm: true`. MCP cannot open Stripe. Signup credit covers at most 50% of a full-audit quote.                                                                |
| Private repo import fails             | GitHub: install the GitHub App or connect GitHub. GitLab.com: connect GitLab. Public repos can clone without credentials.                                                                           |
| GitLab status did not block the merge | QuillShield posts **QuillShield Check**. Requiring that status is a GitLab project setting.                                                                                                         |
| Ask AI 503                            | Platform LLM unavailable. Retry later or use Support.                                                                                                                                               |

More: [CI/CD Checks](https://www.quillaudits.com/quillshield/guides/guides/ci-cd-checks) and [Troubleshooting](https://www.quillaudits.com/quillshield/guides/reference/troubleshooting).


---

# 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://www.quillaudits.com/quillshield/help-center/integrations/why-isnt-my-integration-working.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.
