> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/troubleshooting/deployment-issues/globals-and-accounts-issues.md). # How to resolve deployment issues related to globals and accounts Learn how to resolve deployment issues involving deprecated, restricted, or unset globals and accounts. When deploying or redeploying a pipeline, you might encounter errors related to **deprecated accounts or globals, restricted availability, or missing values**. Below you’ll find the possible error messages and how to resolve each case. ### **Deprecated accounts or globals** **Error message:** * “Deprecated accounts cannot be used” * “Deprecated globals cannot be used” This error appears when a global or account has been marked as deprecated. This action is irreversible. **To resolve:** * Update the pipeline and replace the deprecated account or global with an available one. ### **Accounts or globals not assigned to a project** **Error message:** * “Accounts not assigned to this project cannot be used” * “Globals not assigned to this project cannot be used” This error occurs when a global or account is restricted to specific projects, and the pipeline is being deployed in a project where it’s not available. This usually occurs when the pipeline is moved from a project to another. **To resolve, choose one of the following:** * Make the account or global available in the project where the pipeline is deployed, or * Update the pipeline to use accounts or globals already associated with the project. ## **Account or global value not set** **Error message:** * “Global value hasn’t been set” * “Account value hasn’t been set” This error occurs when the account or global value is missing in the environment where the pipeline is being deployed. **To resolve, choose one of the following:** * Edit the account or global to add the required values for the target environment, or * Update the pipeline to reference accounts or globals that already have values defined for that environment. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/troubleshooting/deployment-issues/globals-and-accounts-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.