> 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/project-history.md). # Project History On the Project History page, you can view a chronological overview of high-level activities for your cloud project. The Project History page shows details about the following changes to your project: * Deployments and CI/CD flow deployments. * Pulling and pushing changes between a flexible environment and its mainline environment. * Adding or removing environments. * Project plan changes. * Transitions between shared and dedicated resources. * Database restores. * Product upgrades (manual and automatic). This is to provide you with better oversight and control over your project.

Project History overview — Project History page

## Viewing Activity Details To get a detailed view of an activity, click the button on the right side of the entry. For each activity, you can see the following information: * The type of activity * Information about the activity * Who started the activity * When the activity was started * When the activity ended * The status of the activity (In Progress, Completed, or Failed) You can copy the activity ID to your clipboard using the clipboard icon on each entry. This is useful when contacting support. For deployments, CI/CD flow deployments, pull/push changes, and upgrades, clicking **See more** opens a detail page with logs, timestamps, and error information.

For upgrades, clicking **See more** redirects to an Upgrade Details page where you can see details about how the upgrade went.

Click **See activity** to view a dialog showing the stages and tasks for environment changes, plan updates, resource moves, or database restores.

Activity dialog — Activity details dialog

--- # 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/project-history.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.