> 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/troubleshooting-backoffice.md).
# The Umbraco Backoffice
An error in the Backoffice often looks like this:
Errors in the backoffice can be presented in many different ways, the most common ones are
* Errors when doing a content transfer / restore
* A blank page when visiting the backoffice
* Missing sections / trees
## If the error is during a content transfer / restore
Start by clicking "View more details", often it will give you a link to a specific article with a guide on how to fix it. We have some guides on how to fix the most common errors below:
* [Schema mismatch](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/schema-mismatches.md)
* [Dependency Exception](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/dependency-exceptions.md)
* [SQL Timeouts](https://docs.umbraco.com/umbraco-deploy/deploy-settings#timeout-settings)
* [Media path too long](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/path-too-long-exception.md)
If your issue is not covered above, here are some general guidelines on what you should do when you have content transfer / restore errors:
The first thing to ensure is that any schema changes have been pushed through Git or deployed between environments so the environments are in sync.
Another thing to check would be the log files. Relevant information can often be found in the [umbracoTraceLogs](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md#umbraco-logs) for both the source and target environments, so make sure to check both.
If you have issues with new user emails/Umbraco Forms emails not being sent, check your SMTP settings for correct configuration. Make sure to read the [SMTP Settings](/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/smtp-settings.md) article.
## If the error is something not loading in the backoffice
There can be different causes for this issue, so we don't have specific guides. However, here are some things to check to narrow it down:
* Do you have any rewrite rules? Often rewrite rules that are not set up correctly will cause issues with the backoffice, make sure that the following are negated:
* `^/umbraco`
* `^/DependencyHandler.axd`
* `^/App_Plugins`
* You can see examples of how to set up rewrites correctly in the [Rewrites on Cloud](/umbraco-cloud/go-live/manage-hostnames/rewrites-on-cloud.md) article.
* Do you get any errors in your browser console that may help you figure it out?
* Do you get any errors in your umbracoTraceLog?
* If something isn't loading after a package was installed it could be because the package overwrites something like the dashboard.config file - try to turn the package off and see if that helps.
---
# 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/troubleshooting-backoffice.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.
