> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/administer/environments/known-limitations.md).

# Known limitations

What Environments don't support yet during the Preview, and how to work around each limitation.

Environments are in Preview, and n8n is actively improving and extending them. Many of these limitations are temporary. Each entry names a workaround where one exists.

{% hint style="info" %}
**Preview status**

Environments are in Preview and may change in future releases. Try them on test instances before you set them up for your production instances.
{% endhint %}

## Enterprise readiness

Environments have **Limited enterprise readiness**. They don't yet support the following Enterprise capabilities:

* **Multi-main:** Environments don't support [multi-main setups](https://docs.n8n.io/deploy/host-n8n/configure-n8n/scaling/enable-queue-mode.md#multi-main-setup). Support is planned.
* **Log streaming:** promote, apply, and review events don't reach [log streaming](https://docs.n8n.io/administer/observe-and-log/stream-logs-to-external-systems.md) destinations. Support is planned.
* **Public API:** the public API doesn't cover promotion reviews. Support is planned.
* **External secrets:** provider access tokens can't come from an [external secrets vault](https://docs.n8n.io/administer/manage-credentials/use-external-secret-stores.md). Support is planned.

## Cross-project dependencies

Workflows can use resources from outside their project: sub-workflows from another team project, and credentials that another project owns and shares with them. Data tables and project variables always belong to one project.

* **Sub-workflows from another project:** a project promote only references them, so they must already exist on the target instance.
* **Credentials owned by another project:** a project promote includes them, but a project apply can only use them if they already exist on the target instance with the same ID, for example from an earlier apply of their project, and are shared with the project. If they're missing, Apply blocks, and you can't create them from **Blockers**.

**Workaround:** promote and apply the project that owns the shared resources first, or use an instance promote and instance apply, which include every team project. An instance apply overwrites every team project on the target, so see [Instance apply](https://docs.n8n.io/administer/environments/apply-changes.md#instance-apply) first. Credentials owned by a personal project never travel. Move them to a team project on the source instance before you promote.

## Moving workflows and folders between projects

A project promote or project apply can't move workflows or folders from one project to another. Moves within a project work. Support for moves in a project promote and project apply is planned.

**Workaround:** use an instance promote and instance apply. They move the existing workflows and folders on the target instance to the project that the branch holds them in, so workflows keep their ID, version history, and executions there. An instance apply overwrites every team project on the target, so see [Instance apply](https://docs.n8n.io/administer/environments/apply-changes.md#instance-apply) first.

## Project-specific environments

Environments currently cover the whole instance. Environments for individual projects are planned.

## Roles that can use Environments

Currently, only instance owners and instance admins can set up environments, promote, apply, and review promotions. Support for project roles is planned.

## Supported Git providers

Environments currently have two provider types: Generic Git and GitLab. Dedicated GitHub and Bitbucket providers are planned.

**Workaround:** connect GitHub, Bitbucket, and other Git hosts with [Generic Git](https://docs.n8n.io/administer/environments/git-based-promotion/generic-git.md). Promotion reviews aren't available there yet.

## Agent support

Promote and apply don't include agents yet. Support is in development.

## Personal projects

Promote and apply cover team projects only.

**Workaround:** move the workflows you want to promote to a team project.

## Workflow descriptions

Promote doesn't include a workflow's description.

**Workaround:** update the description on the target instance.

## Promoting projects without workflows

A project promote needs at least one workflow, so you can't promote an empty project on its own.

**Workaround:** use an instance promote, which includes every team project. Then, on the target, [add the missing project from the environment](https://docs.n8n.io/administer/environments/apply-changes.md#add-missing-projects).

## Selecting dependencies

n8n includes every credential, variable, data table, and tag that the selected workflows use, except credentials owned by a personal project. You can't select dependencies yourself, and you can't promote a credential, variable, data table, or tag on its own. Selecting dependencies is planned.

**Workaround:** promote a workflow that uses them.

## Credential settings

Promote doesn't include whether a credential is shared with all users and projects, or whether each user connects their own account to it.

**Workaround:** on the target instance, edit the credential and set these options again.

## Updating an open promotion review

n8n can't push changes to an open promotion review. For example, if a reviewer requests changes on GitLab, a new promote can't add them to the review. Pushing changes to an open promotion review from n8n is planned.

**Workaround:** close the merge request on GitLab, open **Reviews** so n8n picks up the closed status, then promote again to open a new review. n8n can't close a review itself yet.

## Feature branch names

n8n names feature branches `n8n-promotion/<timestamp>`. You can't choose the name yet. Custom branch names are planned.

## Promotion review status

n8n updates the status of promotion reviews from the Git host when you open **Reviews**. Changes on the Git host don't appear in n8n until then.

## GitLab approval rules

n8n opens and approves merge requests with the same GitLab token. GitLab approval rules that stop authors from approving their own merge requests block **Approve and merge**.

**Workaround:** adjust the approval rules, or merge on GitLab. See [Promotion reviews](https://docs.n8n.io/administer/environments/promotion-reviews.md#n8n-acts-as-the-tokens-user).

## Related resources

* [Environments](https://docs.n8n.io/administer/environments.md)
* [Plan your environments](https://docs.n8n.io/administer/environments/plan-your-environments.md)
* [Your first promotion](https://docs.n8n.io/administer/environments/first-promotion.md)
* [Promote changes](https://docs.n8n.io/administer/environments/promote-changes.md)
* [Apply changes](https://docs.n8n.io/administer/environments/apply-changes.md)
* [Promotion reviews](https://docs.n8n.io/administer/environments/promotion-reviews.md)
* [Git-based promotion](https://docs.n8n.io/administer/environments/git-based-promotion.md)
* [Upgrade from Environments (Classic)](https://docs.n8n.io/administer/environments/upgrade-from-environments-classic.md)
