# Activity and history

The project's **Activity** page shows a list of the analyses that have been performed on your project. This covers all historical data except for that which has been cleaned up by the [Project data lifecycle](/sonarqube-cloud/managing-your-projects/project-data-lifecycle.md) process.

Graphs on the activity page help you understand the evolution of up to three measures of your choice against each other. Graph mouseovers show the measure values and events associated with particular analyses.

<figure><img src="/files/t1v3pVDbIhjdx3JHc5FT" alt=""><figcaption></figcaption></figure>

## Events <a href="#events" id="events"></a>

There are four types of events:

* **Quality Gate**: the status of your quality gate has changed. See the [Understanding quality gates](/sonarqube-cloud/standards/managing-quality-gates/introduction-to-quality-gates.md) page for details.
* **Profile**: the quality profile used to analyze your project has changed - either the profile was edited, or a different profile was used to analyze the project. See the [Understanding quality profiles](/sonarqube-cloud/standards/managing-quality-profiles/understanding-quality-profiles.md) page for details.
* **Version**: the project’s version changed.
* **Other**: an event was manually created on a snapshot. See the page about [Managing project history](/sonarqube-cloud/managing-your-projects/managing-project-history.md).

See the[Main branch analysis](/sonarqube-cloud/analyzing-source-code/branch-analysis/main-branch-analysis.md) and [Viewing your first analysis' results](/sonarqube-cloud/getting-started/first-analysis.md) pages to for more information.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/activity-and-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.