> 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/sustainability-best-practices/backend/common-pitfalls.md). # Common pitfalls Tackling common pitfalls in implementing an Umbraco solution is integral within the realm of sustainable system design. Addressing the [common pitfalls](https://docs.umbraco.com/umbraco-cms/reference/common-pitfalls) stands as a cornerstone for crafting systems that not only excel in functionality but also uphold environmental consciousness. By sidestepping common errors and inefficiencies, developers proactively ensure the optimal use of resources, curbing energy consumption, and extending the system's lifespan. Such an approach seamlessly aligns with the tenets of sustainable system design, which prioritizes efficiency and waste reduction for long-term system viability. Navigating these challenges not only fine-tunes performance but also advances the cause of a more sustainable digital ecosystem. In doing so, software solutions effortlessly complement the broader goal of environmental preservation. --- # 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/sustainability-best-practices/backend/common-pitfalls.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.