> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qlty.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Analysis is paused

<Warning>
  Qlty is not analyzing this project. New commits and pull requests are not analyzed, and no
  commit statuses are posted, until analysis resumes.
</Warning>

## What happened

Qlty could not check out your repository. After repeated checkout failures, Qlty stops attempting to analyze your codebase rather than retrying indefinitely.

## Why it happened

There are a few reasons why Qlty might not be able to clone your repository:

* **A GitHub outage.** If GitHub was unavailable while your builds ran, Qlty could not reach your repository. Qlty does not resume on its own once GitHub recovers.
* **The Qlty GitHub App no longer has access.** The app was uninstalled, or its repository access was changed and no longer includes this repository.
* **The repository was transferred to another owner.**
* **The repository was deleted.**

If the cause applies to your whole GitHub organization, other projects in your workspace are likely paused as well.

## How to fix it

**Start by queueing a build.** Click **Run build** on the alert, or **Build** on the project's [Builds page](/cloud/analysis-frequency#triggering-analysis-manually).

Analysis resumes on the first build that succeeds, and the alert clears with it. This is the right place to start because a pause often outlasts its cause: after a GitHub outage is resolved, nothing else is wrong, and one successful build is all it takes. If the build fails instead, you know the problem is still present.

If the build fails, work through these steps.

<Steps titleSize="h3">
  <Step title="Confirm GitHub App access">
    The [Qlty GitHub App](/cloud/github-app) is installed on a GitHub organization, and that installation grants access to either **All repositories** or **Only select repositories**. Analysis breaks when the app is uninstalled, or when the repository is no longer in the selected list.

    In Qlty, go to **Settings > General > Connections** for your workspace. It shows the Qlty GitHub App and its Repository Access, each with a link out to GitHub to change the configuration.
  </Step>

  <Step title="Re-sync with GitHub">
    If the repository was transferred to another owner, Qlty does not pick that up on its own. Go to **Project Settings > General** and click **Re-sync** under **Re-Sync with GitHub**.
  </Step>
</Steps>

Then queue another build. If builds still fail with a repository error after access looks correct, [contact support](/cloud/support) with the project name and a failing build URL.

## Why pushing new commits does not help

While analysis is paused, Qlty only runs builds that someone asks for directly. Pushes, pull requests, and [scheduled analysis](/cloud/analysis-frequency) are all ignored, so waiting for the next commit will never resume analysis on its own.

This keeps a paused project quiet until someone has looked at it, rather than failing on every push.