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

# FAQ and troubleshooting

> Answers to common questions about branches, protected branches, pull requests, previews, and the chat, and what the messages mean when something does not go through.

## Branches and data

> [accordion] Why does my data change affect other branches?
>
> Branches isolate code, not data. Tables, columns, enums, indexes, and rows live in an [environment](https://archie.com/docs/backend/environments.md), and every branch connected to that environment shares it. If you change a table from a branch, the change applies to the data of the environment, and every other branch connected to it sees the change.
>
> That is why the chat asks you to confirm before it changes a table from a branch other than the default. If other branches must not see your data, connect your branch to a separate environment. See [The environment of a branch](https://archie.com/docs/frontend/branching/previews-and-publishing.md#the-environment-of-a-branch).

> [accordion] Why can't I create another branch?
>
> Your plan includes a limited number of extra branches per project. You see "This project reached its limit of extra branches. Delete one or buy more to create another." Delete a branch you no longer need, or add capacity. Nothing you already have is deleted when you reach the limit.

> [accordion] I cannot see the branch chip
>
> The Frontend branch chip appears after the Frontend is generated. Branches and pull requests are visible to Owners, Admins, and Editors. A Viewer does not see them. Ask an Owner or Admin to change your role. See [Permissions](https://archie.com/docs/frontend/branching/permissions.md).

## Protected branches and saving

> [accordion] Why can't I edit a branch?
>
> The branch is probably protected. On a protected branch, changes arrive only through a merge. Create a branch from it with **New branch**, make your changes there, and open a pull request. From the chat, choose **Create branch *name* and continue** when it asks. See [Protected branches](https://archie.com/docs/frontend/branching/protected-branches.md).

> [accordion] The chat stopped and asks me to choose a branch
>
> The branch the chat was about to write to is protected. Choose **Create branch *name* and continue** or **Use another branch**. See [The chat and branches](https://archie.com/docs/frontend/branching/chat-and-branches.md#protected-branches-the-chat-asks-where-to-continue).

> [accordion] My visual edits or theme changes were not saved
>
> The branch was protected, is a merge being resolved, or no longer exists. The editors tell you which. If the branch became protected, they keep your edits and tell you to create a branch from here to save them. Select **Create branch from *branch*** to keep your edits.
>
> The design system belongs to the project, so all branches share it. Applying it writes only to the branch you are on. Other branches show "The design system changed" until they apply it.

> [accordion] "This branch changed since you opened it"
>
> Someone else saved to the same branch while you were editing. Choose **Keep mine in a new branch** to keep your work separately, or **Reload and re-apply my changes** to put your edits on top of the new version.

## Pull requests and merging

> [accordion] I merged, but my site did not change
>
> A merge only moves code between branches. It never publishes the site and never deploys a service. Publish the Frontend with **Publish**, or deploy the service with **Deploy**. See [Previews, sharing, and publishing](https://archie.com/docs/frontend/branching/previews-and-publishing.md).

> [accordion] A merge says the target moved
>
> You see a message such as "*main* moved since *feature* was created". A direct merge into a protected branch works only when your branch contains everything that is in the target. Bring the target's changes into your branch, or open a pull request.

> [accordion] A pull request merge looks stuck
>
> After a merge, the target branch can take a few seconds to be ready. The page says "Finishing entering *target*", and nobody can write to the target meanwhile. If the page offers **Retry**, use it. If you see "This merge got stuck and can't be retried from here", contact support or an Owner of the project.

> [accordion] I cannot apply a suggestion
>
> A suggestion cannot be applied when the code changed since the review, when it was already applied, when two suggestions change the same lines, or when the branch is protected. Apply the change by hand or request another review.

> [accordion] Does Archie Reviewer use credits?
>
> Yes. Each review consumes credits, and the cost depends on the size of the pull request. Applying a suggestion is free, and a commit that Archie already reviewed is not charged again. See [Archie Reviewer](https://archie.com/docs/frontend/branching/archie-reviewer.md).

## Sharing and services

> [accordion] Who can open a share link, and until when?
>
> Anyone with the link can open it until its expiration date. After that, the link no longer opens. You can also revoke a link at any time. See [Share a preview](https://archie.com/docs/frontend/branching/previews-and-publishing.md).

> [accordion] I cannot create a share link right after a merge
>
> While a branch is still updating after a merge, you see "*branch* is updating after a merge. You can share when it finishes." Try again in a few seconds.

> [accordion] The query of my service works in one environment but not in another
>
> Each environment exposes the services deployed to it in its own GraphQL API. Until you deploy the service to the second environment, its operations are not there. See [Deploy a service from a branch](https://archie.com/docs/backend/logic/branches.md#deploy-a-service-from-a-branch).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.