# Could not get the code

> no_source, clone_failed, no_branch, empty_repo, no_access, too_big — what to do when a deploy cannot get the code.

Source: https://livops.dev/en/docs/error-source

With these errors the build has not started yet: we stopped while getting the code.

## `no_source` and `source_gone`

The uploaded files are missing or were removed. Upload the folder again, or connect a repository in **Settings → Source**.

## `clone_failed`

The repository could not be cloned. Usually:

- the repository is private and access was revoked;
- its address changed (renamed or moved);
- a submodule points to a private repository.

Connect GitHub or GitLab again in the cabinet, then press **Retry**.

## `no_branch`

The branch was not found. If the repository is still empty, push first. If the branch is named differently (`master` or `main`), fix it in **Settings**. The deploy log lists the branches the repository does have.

## `empty_repo`

The repository is empty: no code has been pushed to it yet. Push your code. If the repository is connected through GitHub or GitLab, the push starts the deploy itself; otherwise press **Retry** afterwards.

## `no_access`

No access to the repository. Connect the provider again. For an organisation's repository, grant the Livops app access in the organisation's settings.

## `too_big`

The uploaded folder is too large. Usually it holds `node_modules`, `.venv`, `dist` or videos. Remove them — we install dependencies ourselves. Put large files in [Files](https://livops.dev/en/docs/files).
