> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/maintenance/maintenance-history.md).

# Maintenance history

The **Maintenance** tab features a **Maintenance history** button, displaying detailed information about past maintenance, including changes made, reasons for the maintenance, and data of the person responsible for the update.

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

{% hint style="info" %}
Always provide the reason for enabling or disabling maintenance or displaying a warning. This reason will be automatically recorded in the maintenance history, ensuring transparency and traceability of changes.
{% endhint %}

***

### Logs

This section allows you to consult environment information based on applied filters, displaying events and actions related to the client.

***

### Client Summary

By clicking this option, a modal will appear with the client’s data. If desired, click “**Generate PDF**” to download this information.

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


---

# 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 dynamically by asking a question.

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

```
GET https://docs.skyone.cloud/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/maintenance/maintenance-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.