Update a Mate Agent

Update a runtime without losing track of the automations and services that depend on it. Use a package compatible with the installed Autom Center version.

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 [email protected] before starting.

Prepare the maintenance window

Record the Agent name, host, installed version, service account, time zone and any default assignment. Identify Hyperflows, service deployments and scheduled work using it. Agree how the affected work will be handled while the runtime is unavailable.

Prepare the target package, supported update sequence, configuration backup and recovery procedure. Keep a test for each important dependency: for example, one API read, one local file operation and one script interpreter used by the workload.

Apply the update

1. Confirm that the affected operational work is ready for maintenance. Check active executions before stopping runtime services.

2. Stop the Agent services using the procedure supplied with the update package.

3. Check service state and resolve a component that failed to stop before updating its files.

4. Run the approved update package with its required privileges and retain the result.

5. Start the Agent services using the package's sequence.

6. Open Manage → Mate Agents and confirm that the intended Agent returns with the target version.

Earlier Windows packages provide stop_services.bat and start_services.bat in the Agent installation directory. Use these only where they are supplied for the installed package and their scope is understood. Do not copy a historical script or stop services by a broad name pattern.

Check configuration and work

Check	What to compare
Identity	Service account, filesystem permissions and required task privileges
Connection	Intended Center/workspace, certificate trust and target access
Runtime details	Version, default assignment and time zone
Dependencies	Required interpreter/package versions and service-account environment
Execution	Controlled test output and action-level logs
Health	Relevant Agent Service state and a recent metrics timestamp

Restart affected workloads only after the checks pass. When several Agents exist, validate the updated one explicitly so another runtime does not conceal a problem.

Expected result

The Agent reports the intended version, retains the required configuration and completes the same controlled checks used before the update. Save the before/after versions, package identifier, maintenance time and test record.

Recovery

If the Agent does not return, inspect service startup logs, registration and certificate settings before changing workflow logic. If an integration alone fails, inspect its credentials and dependencies. Restore the compatible Agent/configuration combination using the approved recovery procedure when acceptance checks cannot be completed.

Use network troubleshooting and time-zone correlation to keep the investigation focused.

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 [email protected] 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.