# How to resolve deployment issues related to 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.