> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/vault/vault-features/backup/understanding-backup-behavior.md).

# Understanding Backup Behavior

## Understanding **Backup Behavior** for Polymorphic Fields, Special Objects, and Ignored Objects

As part of the backup process, certain fields and objects are handled differently to ensure data integrity and system efficiency. The following changes outline how these elements are handled:

1. **Polymorphic Fields**
   * When a backup is performed, **polymorphic fields are not included**.
   * Since these fields reference multiple object types dynamically, excluding them helps maintain data consistency.
2. **Special Objects**
   * When a backup is performed, **special objects are not included** in the backup.
   * These objects are **not** displayed in the schema, as they are excluded due to system limitations or unique structural constraints.
3. **Ignored Objects**
   * **Ignored objects are included** in the backup.
   * These objects **are visible** in the schema, ensuring transparency in the backup process.


---

# 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://knowledgebase.autorabit.com/product-guides/vault/vault-features/backup/understanding-backup-behavior.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.