> For the complete documentation index, see [llms.txt](https://docs.envio.dev/llms.txt).

# Envio Cloud Troubleshooting

Answers to the most common problems when deploying and running indexers on Envio Cloud. For issues with running your indexer locally, see [Common Issues](https://docs.envio.dev/docs/HyperIndex/common-issues.md).

### Why does my indexer build locally but fail on Envio Cloud?

First, make sure your deployment meets the [requirements](https://docs.envio.dev/docs/HyperIndex/hosted-service-deployment.md#requirements).

Envio Cloud builds from the commit on GitHub and only uploads the folder set as **Indexer Directory** in your indexer settings. Check the following:

- **Imports outside the indexer directory**: code imported from a folder above the Indexer Directory is not uploaded. Move shared code inside the Indexer Directory, or set the Indexer Directory to a folder that contains everything the indexer imports.
- **Files that are not committed**: anything in `.gitignore` or not pushed to the deployment branch is not part of the build.
- **Skipped folders and files**: folders named `generated` or `node_modules` are skipped at any depth, as are dotfiles and dot folders other than `.npmrc`. Keep files the indexer needs, such as ABIs, in a folder with a different name, and set environment variables in the [Environment Variables tab](https://docs.envio.dev/docs/HyperIndex/hosted-service-deployment.md#environment-variables-tab) rather than a `.env` file.
- **Envio version**: `envio` must be listed in the `package.json` inside the Indexer Directory with an exact version, such as `"envio": "x.y.z"`, that meets the [version requirements](https://docs.envio.dev/docs/HyperIndex/hosted-service-deployment.md#requirements). Values such as `~x.y.z`, `latest` or `workspace:*` are rejected, and the commit shows "Invalid version" with the message "The Envio version is not supported".
- **Dependency versions**: Envio Cloud resolves dependencies on every build and does not use your `pnpm-lock.yaml`, so a version range can resolve to a newer release than the one you run locally. Pin exact versions if the build differs from your local setup.

### Why didn't my push start a deployment?

- **Branch name**: the branch you pushed to must match **Git Release Branch** in your indexer settings exactly, including case.
- **Automatic deployments**: check that **Automatically Deploy On Push** is enabled in your indexer settings. When it is disabled, deploy a commit from the **Recent Commits** section instead.
- **Member role**: pushes from members with the `reader` role do not start a deployment automatically. An admin can deploy the commit from **Recent Commits**.
- **Deployment limit**: each indexer can have 3 deployments. Delete an old deployment, then deploy the commit from **Recent Commits**. See [Deployment Limits](https://docs.envio.dev/docs/HyperIndex/hosted-service-deployment.md#deployment-limits).
- **Paused indexer**: pushes to a paused indexer do not start a deployment. See [Why is my indexer paused?](#why-is-my-indexer-paused)
- **Indexer Directory or Config File**: if either path is wrong, the commit shows "Failed to download" or "Missing config". The Config File path is relative to the Indexer Directory. After changing the Indexer Directory, push a new commit.
- **Repository access**: the Envio Deployments GitHub App must have access to the repository. Add it in the app's settings on GitHub.

### Why can't I see my organisation or repository in Envio Cloud?

Installing the GitHub App adds the person who installed it. Other members of the GitHub organisation must be added by an organisation admin on the **Members** page before they can see the organisation, its repositories and indexers. Until then they see "You are not a member of this team". See [Access Control](https://docs.envio.dev/docs/HyperIndex/organisation-setup.md#access-control).

Only people who are members of the GitHub organisation can be added.

### How do I add someone to my organisation?

An organisation admin can select **Add** next to the person on the **Members** page. The page lists the members of your GitHub organisation, so the person must be a member there first. See [Adding Members](https://docs.envio.dev/docs/HyperIndex/organisation-setup.md#adding-members).

### How do I remove someone from my organisation?

An organisation admin can select **Disable** next to the member on the **Members** page. The member loses access to the organisation in Envio Cloud. Admins can enable them again while they are still a member of the GitHub organisation.

### Why is my indexer paused?

An indexer is most often paused because of outstanding payments. Settle your account, then contact the Envio team to resume indexing. Indexers on the development plan are also scaled down when they pass the [fair usage limits](https://docs.envio.dev/docs/HyperIndex/hosted-service-deployment.md#development-plan-fair-usage-policy).

## Related Documentation

- **[Deploying](https://docs.envio.dev/docs/HyperIndex/hosted-service-deployment.md)** - Deploy, update and configure your indexer
- **[Monitoring](https://docs.envio.dev/docs/HyperIndex/hosted-service-monitoring.md)** - Track logs, sync status and alerts
- **[Organisation Setup](https://docs.envio.dev/docs/HyperIndex/organisation-setup.md)** - Create an organisation and manage members
- **[Pricing & Billing](https://docs.envio.dev/docs/HyperIndex/hosted-service-billing.md)** - Compare plans and see feature availability
- **[Common Issues](https://docs.envio.dev/docs/HyperIndex/common-issues.md)** - Troubleshoot local and runtime indexer issues