> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/deployment-failed.md).

# Troubleshooting deployments failing with no error message

This error might pop up if your project's files were recently upgraded/updated to the latest version. Any deployment you try will end up failing instantly.

![Deployment failed](https://3739769070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPzKn70Piyd2fd5UkYZGf%2Fuploads%2Fgit-blob-b2f1b665ae1df3e01fab36b7909d1d92703b0596%2Fdeployment-failed.png?alt=media)

## Cause

This error is caused by leftover upgrade markers interfering with the Deploy process. This might happen if your environment was restarted during the upgrade, or the upgrade process encountered some issues.

## Fixing

In order to fix this issue, you would need to use [KUDU](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/power-tools.md) to remove the leftover marker files.

1. Access KUDU on the source environment (the one you are deploying from)
2. Navigate to `site` > `locks` folder
3. In the folder, there should be a file named `upgrading`, `upgrade-failed` or `failed-upgrade`. Remove these files.
4. Repeat the operation on the target environment - it might also have the leftover marker

Once the leftover marker files are removed, your deployments should go through without problems.


---

# 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.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/deployment-failed.md?ask=<question>&goal=<user_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.