# The Umbraco Cloud Portal
An error in the Cloud Portal often looks like this:
Error on cloud
Errors in the Cloud Portal are shown as a colored indicator of an environment. An environment can have three colors:
* **Green** - this is the "healthy" state where everything is fine
* **Yellow** - this is the "busy" state that normally occurs when a deployment is in process or an environment is being added
* **Red** - this is the "error" state which normally has information about what went wrong
{% hint style="info" %}
When your environment has an error and you try to deploy again it will not be able to. The error will **always** need to be resolved before another deployment can be started.
{% endhint %}
## My environment is red. What do I do?
The first thing to check is what type of error it is, you can do so by clicking the **More info** button on the state:
We have some guides on how to fix the most common errors below:
* [Some artifacts collide on unique identifiers](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/structure-error.md)
* [Duplicate dictionary](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/duplicate-dictionary-items.md)
* [Baseline merge issues](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts.md)
* [Colliding Data Types](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/colliding-datatypes.md)
* [Type not found](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/type-not-found.md)
* [Deployment fails instantly with no message](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/deployment-failed.md)
If your issue is not covered above here are some general guidelines on what you should do when you have error states on Cloud environments:
An environment is in an error state because the Umbraco Deploy engine sets markers on the environment. The green one sets a `deploy` marker, the yellow one a `deploy-progress` marker, and the red one a `deploy-failed` marker.
Sometimes a deployment will fail due to another deployment in progress. You'll need to wait a bit before you can kick in another deployment. By doing this, the deployment will go from failure to complete without needing to do anything extra - read more about [manual data extractions](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/power-tools/manual-extractions.md).
Often the deployment fails because of an error that won't be fixed by re-deploying. In these cases, you will need to have a look at the log files.
You can check both the regular [umbracoTraceLogs](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md#umbraco-logs) and the [deploy logs](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md#deploy-logs).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-portal.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.