> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/seascape-for-notes/seascape-flex/updating-existing-archives.md).
# Updating existing archives
Updating Seascape web viewer version for all existing archives
Open the Seascape Flex control panel and click **Update archives**.
Next, a new window will appear showing our Seascape viewer Updater tool.
Choose the root folder of your archives, and click on **Update** button.
Once the update is complete, all existing archives will be updated to include the latest versions of the Flex design elements and the Seascape viewer.
{% hint style="info" %}
For the changes to take affect, you will need to restart the Elastic search and Flex services
{% endhint %}
Description of the different options:
* **Update catalog only** - If you select the "Update catalog only" option, only the catalog page will be updated. Otherwise the Archive Updater will update both the catalog page and every database in the archive.
* **Force update** - It will force an update for the catalog page and every database in the archive.
---
# 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.swingsoftware.com/seascape-for-notes/seascape-flex/updating-existing-archives.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.
