> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/administration-and-runtimes/update-autom-center.md).

# Update Autom Center

Update an existing customer-managed Autom Center while preserving its configuration and a tested recovery path. An infrastructure administrator should own the maintenance window and coordinate dependent execution work.

Dublin package availability — 13 October 2026: the Dublin on-premises installer is not yet available. The steps below apply when you have a released package for your selected component and version. Confirm package availability and compatibility with <support@autommate.com> before starting.

## Plan the update

Record the starting Center and Mate Agent versions, the target versions and the supported upgrade path. Obtain the matching update package and release instructions. A fresh installer and an update package serve different purposes; do not substitute one for the other.

Before the window:

* Review release changes and component compatibility.
* List scheduled work, active executions and dependent integrations.
* Agree how new work will be handled during maintenance and how in-flight work will finish or be handled.
* Back up the configuration and data required by the release's recovery procedure; confirm that the backup can be restored.
* Record one small, repeatable test and its normal result.

## Apply the package

1. Confirm that the maintenance window and recovery checkpoint are ready.
2. Use the release's procedure to stop the required platform services. Check their actual state before proceeding.
3. Run the approved update package with its required privileges.
4. Capture the installer result. If it fails, preserve the log and follow the approved recovery procedure rather than repeatedly rerunning it.
5. Restart components in the sequence required by the package.
6. Open Autom Center and confirm the reported platform version.

Earlier Windows update guides name **Apache Tomcat** and **Autom Mate Service**. Service names and sequencing must match the installed release; they are not a blanket instruction to stop similarly named services on another host.

## Validate before reopening normal work

| Check                  | Expected result                                                            |
| ---------------------- | -------------------------------------------------------------------------- |
| Browser access         | Configured URL, certificate and sign-in work                               |
| Version                | Platform reports the target build                                          |
| Runtime connection     | Intended Mate Agents appear and their required services are available      |
| Existing configuration | Representative flows, credentials and schedules are present                |
| Controlled test        | The pre-update test returns its expected result and its logs are available |
| Operations             | Approved scheduled work resumes at the intended time                       |

Keep the maintenance record with the before/after versions, package name, backup reference, test identifier and outcome. Use [time-zone correlation](/userguide/administration-and-runtimes/time-zones.md) when comparing logs across systems.

## If validation fails

Identify whether the failure affects platform access, runtime communication or a particular integration. Preserve the first failing log and the update output. Use the defined rollback procedure if the acceptance checks cannot be met within the maintenance window.

Do not assume an older binary can read a database migrated by a newer release. Recovery must restore a compatible combination of application, configuration and data.

### Prepare a snapshot recovery checkpoint

Before updating a self-managed installation, plan a full-server snapshot for every host that contains Autom Center, the database or a Mate Agent. If the components run on separate hosts, include all of those hosts in the same recovery plan.

Agree the consistency checkpoint and the supported capture/restore sequence with the infrastructure administrator and <support@autommate.com> before starting. Include the current and target versions, component-to-host map, maintenance window, snapshot identifiers and the checks required before normal schedules and requests resume.

A snapshot identifies a recovery point; it does not by itself prove that the application and database can be restored consistently. Use the recovery procedure approved for the selected release and validate the restored versions, Agent connectivity and a controlled execution before reopening normal work.