> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-program-overview/auto-backup.md).

# Auto Backup

Depence has a feature to frequently save your project as a backup automatically. 

For this purpose, you will find the information "Backup Off" or "Backup On" in the lower status bar.\
You can click on this label to change the status from Backup Off to Backup On.

When a backup is executed, another subfolder "Backup" is automatically created in the project folder and the current project status is saved there.

You can set the options for the interval and the lead time at which a backup is to be created in the Application Settings.

<figure><img src="https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/BgP76UnKhaXA2SRtvOrV/image.png" alt=""><figcaption></figcaption></figure>

Before the system creates a backup, a countdown dialogue appears in which you can cancel the process with "Cancel" or carry out the backup process again with "Save". You can change the settings with "Setup".

<figure><img src="https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/jiuEwgmlGImrPDkxjNMA/image.png" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.depence.com/depence-program-overview/auto-backup.md?ask=<question>&goal=<user_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.