> 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/developer-guide/development-cycle/overview/deployment/how-to-resolve-pipeline-issues-after-deployment.md).

# How to resolve pipeline issues after deployment

Learn how to identify and resolve pipeline issues in Run using the warnings shown on each pipeline card.

## **Why pipelines show warnings**

While a pipeline runs in the Test or Prod environment, Digibee monitors it for common issues, such as configuration changes, memory limits, and deployment problems. When it detects one, it adds a warning icon to the pipeline card in the Run page.

## **How it works**

Hover over the warning icon on a pipeline card to see a quick summary of the active warnings in a tooltip. Some warnings only appear in the pipeline details.

![](https://866970526-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjvO5S91EQURCEhbZOuuZ%2Fuploads%2FKsRda9uyUex1Bk3x7Dr8%2Funknown.png?alt=media\&token=66b03b9e-f69a-48c9-8794-41d3427c3fce)

Click the pipeline card to open its details, where the same warnings appear with a full description and, when available, a recommended action.

## **Warning types**

<table><thead><tr><th width="163.40008544921875">Warning type</th><th width="334.7999267578125">Message</th><th width="249.00006103515625">What to do</th></tr></thead><tbody><tr><td><strong>Edited account</strong></td><td>This pipeline is associated with an account that has been edited. We recommend redeploying this pipeline to prevent issues and make sure the pipelines are up to date.</td><td>Select <strong>Redeploy pipeline</strong> to update the pipeline with the latest account configuration.</td></tr><tr><td><strong>Edited global</strong></td><td>This pipeline is associated with a global that has been edited. We recommend redeploying this pipeline to prevent issues and make sure the pipeline is up to date.</td><td>Select <strong>Redeploy pipeline</strong> to apply the latest global configuration.</td></tr><tr><td><strong>Out of memory</strong></td><td>There hasn't been enough memory to process one of the messages of your pipeline. You can try again by using deployments of greater sizes.</td><td>Redeploy the pipeline using a deployment with a larger size.</td></tr><tr><td><strong>Degraded</strong></td><td>The deployment ran, but the pipeline replicas did not come up in time. Redeploy the pipeline to try again.</td><td>Select <strong>Redeploy pipeline</strong> to try the deployment again.</td></tr><tr><td><strong>Redeploy required after moving projects</strong></td><td><p>After moving the pipeline between projects, it's necessary to redeploy it to have access to the updated metrics and logs. </p><p></p><p><em>This warning only appears in the pipeline details. It's not shown in the tooltip.</em></p></td><td>Select <strong>Redeploy pipeline</strong> to restore access to updated metrics and logs.</td></tr><tr><td><strong>Errors</strong></td><td><p>Your pipeline has errors and issues. Your pipeline has encountered an error during execution time. You can review all logs to facilitate troubleshooting. </p><p></p><p><em>This warning only appears in the pipeline details. It's not shown in the tooltip.</em></p></td><td>Select <strong>See all logs</strong> on the warning card to open the pipeline logs and troubleshoot the error.</td></tr></tbody></table>

## **Next steps**

Now that you know what each pipeline warning means, learn how to [redeploy a pipeline](/documentation/developer-guide/development-cycle/overview/deployment/deployments.md) from the Run page.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digibee.com/documentation/developer-guide/development-cycle/overview/deployment/how-to-resolve-pipeline-issues-after-deployment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.