> 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/background-tasks.md). # Background tasks Implementing background tasks or batching up requests to run in sustainable cloud regions and during off-peak hours of power consumption is a commendable sustainable system design practice. Implementing background tasks or batching up requests to run in sustainable cloud regions and during off-peak hours of power consumption is a commendable practice. By strategically scheduling resource-intensive tasks in regions powered by renewable energy sources, organizations can minimize their carbon footprint. The same effect will be seen by scheduling intensive tasks during times of reduced energy demand. This approach not only optimizes the use of available resources but also aligns with the broader objectives of sustainable development. By harnessing the power of cloud computing in an environmentally responsible manner, businesses can make substantial strides toward creating more energy-efficient systems. And these systems can operate in harmony with eco-conscious principles, reducing their overall environmental impact. --- # 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/background-tasks.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.