Loading the documentation…
Use Admin > Update > Updates on a self-managed installation to update DataMind OS. An update has two steps, in this order: the Installer, the tool that installs and manages DataMind OS, then DataMind OS itself.
The tab opens with Check for Platform Updates and checks both steps as soon as it opens. Starting an update needs Execute Platform Update; without it you see the same page, read-only, with the line "You can see the updates; starting one needs the permission to run updates." On an installation DataMind manages for you, this tab does not appear; see Update. The same updates from the host side, on the DataMind Installer's own screens, are on Updating.
| Permission | What it lets you do |
|---|---|
| Check for Platform Updates | Open the Updates tab and see both steps and every image. |
| Execute Platform Update | Click Update Installer, Update DataMind OS and Pull images only. |
Platform Administrator holds both permissions; Platform Viewer holds the first. The Update page itself appears on installations that include the platform controls, for roles with View Platform Services or Check for Platform Updates. If DataMind manages your installation, the page shows only the version it runs, with Services and updates are managed by DataMind.
| Badge | What it means |
|---|---|
| Up to date | The installed build is the latest published one. |
| Update available | A newer build is published. |
| Updating | This step's update is running. |
| Check failed | The comparison with the registry failed. The card shows the reason and Retry. |
| Checking | The comparison is running. |
| Not checked | No check result is available, typically while the check is paused because the Installer is replacing itself; the card also shows the Waiting for the Installer lock strip, and the buttons' tooltip reads Refresh to check for updates. |
A build reads one of two ways:
prod-20261018., when the image carries one. DataMind OS images are stamped <channel>-<yyyyMMdd. and the Installer image <channel>-<build number>. The build time follows in smaller type.The DataMind OS card sums up all its images: the shared version when every image carries the same one, otherwise when the newest image was built. Under Latest, it counts how many images are newer, such as "3 of 29 images newer".
The tab checks when it opens and does not check again on its own. Click Refresh after a new release is published.
The cards also show notes when they apply:
The Installer must be updated before DataMind OS. While a newer Installer is published, the DataMind OS card is locked: it reads Update the Installer first and "DataMind OS updates are refused until the newer Installer is applied.", and Update DataMind OS and Pull images only are greyed out. The installation applies the same rule to an update started any other way, such as from the Installer's own screen: a toast titled Installer update required reads Update the Installer first.
Other outcomes:
Update Installer is greyed out while a job runs, when the Installer is already on its latest version, or without Execute Platform Update; hover it to read which.
<n> services will be pulled and recreated: <names>."<names> - expect a short outage for everyone." Shown when a critical service is in the update.While the update runs, each service in the sidebar shows its own place in it, such as its download percentage.
You can leave the page, and even reload it, while the update runs; it keeps going. A banner at the bottom of every page reads Updating DataMind OS with the current step and the time it has run, and View brings you back.
Pull images only downloads the newer images without restarting anything. Use it ahead of a maintenance window, so the update has less to fetch.
It follows the same rules as Update DataMind OS: it waits for the Installer, for a running job, and for something newer to download.
| What you see | What it means |
|---|---|
| The banner DataMind OS updated, "reloading in 5s" | The update finished and replaced the interface. The page reloads by itself; Cancel stops the countdown and Reload now reloads at once. After the reload, a toast reads DataMind OS updated: "You are now on the new version." |
The toast DataMind OS updated, with "Updated: <names>" or "Every service is on its latest image." | The update finished. No reload is needed. |
| Update failed on the card, and the toast or banner DataMind OS update failed | The update did not finish. The reason follows; Open Job logs shows the full output. |
| Update cancelled, and DataMind OS update cancelled | The job was cancelled before it finished. |
| Update no longer tracked, and the toast Update job lost | The Installer no longer tracks this update job, so the page cannot read how it ended. Check the services in the sidebar and click Refresh. |
The result stays on the card until you click Dismiss.
Below the cards, the Images table lists every service with its Image, its Installed and Available builds and its State. The line above it sums the comparison up in one of three forms: "<n> of <m> images have a newer build", "<m> images checked" when nothing is newer, or "All <m> images are on their latest build". The first two carry a ", <n> registry error(s)" suffix while the check hit errors. Counts keep their singular and plural forms: 1 image and 3 images, 1 registry error and 2 registry errors. Hover a build to see its digest.
Only changes keeps the services that need a look: a newer build, a registry error or an image not pulled yet. It is on when something is newer; turn it off to see every image.
| State | What it means |
|---|---|
| Update available | A newer image is published. An update recreates this service. |
| Up to date | The image on this host is the newest published one. |
| Not pulled | The image is not on this host yet, so there is nothing local to compare. Pull images only downloads it. |
| Registry error | The image could not be compared with its registry. Hover the badge to read the reason, then click Refresh. |
Hover it to read why. Update the Installer first means a newer Installer is waiting; Waiting for the Installer means it is being applied. Refresh to check for updates means no check result is available yet. "A job is running. Updates can start once it ends" means another job holds the installation. "Every image is already on its latest build" means there is nothing to update. Without Execute Platform Update, the tooltip reads "Starting an update needs the permission to run updates".
The page appears for roles with View Platform Services or Check for Platform Updates, and the Updates tab opens with Check for Platform Updates. Starting an update needs Execute Platform Update; without it you can read the tab but not start anything. Platform Administrator holds both update permissions, Platform Viewer only the first. On an installation DataMind manages, the page shows only the version it runs.
The Installer is the tool that installs and manages DataMind OS, and the installation refuses DataMind OS updates and pulls while a newer Installer is published and not yet applied. Apply it from the Installer card: it takes under five minutes, DataMind OS keeps running meanwhile, and the DataMind OS card unlocks on its own afterwards.
Not while a newer Installer is waiting. The installation refuses the update with a message to update the Installer first, wherever it was started. Update the Installer, then start the DataMind OS update. See Updating.
Pull images only downloads the newer images and restarts nothing. Update DataMind OS pulls and recreates the services that have a newer image, which is what applies a new version. A pull runs as a job, so you can follow it in Job logs.
Yes. The job runs on the installation, not in the tab. A banner at the bottom of every page reads Updating DataMind OS, and View brings you back; the output is also in Job logs. Leaving or reloading the page does not stop the update.
The update replaced the interface itself, and the confirmation said so before you started. The banner counts down five seconds and reloads the page so the new interface runs; Cancel stops the countdown, and Reload now reloads at once. After the reload, a toast reads "You are now on the new version."
The image carries no version, so the card shows when it was built. Images that carry a version show it, such as prod-20261018.. On the DataMind OS card, a version appears only when every image carries the same one.
The card reads Update failed with the reason, and the toast and banner read DataMind OS update failed. Click Open Job logs for the full output. For the messages this area shows and what to do, see Administration troubleshooting.
The Installer stopped keeping the job's record before its result could be read, for example because the Installer was replaced. The page cannot say how the update ended: check the services in the sidebar and click Refresh. If an update is still available, run it again.
No. The update pulls and recreates every service that has a newer image, and the confirmation lists them. To act on a single service, restart or stop it from the sidebar: see Services and job logs.
Sometimes, briefly. Services are recreated while the update runs, and when a critical service is among them everyone sees a short outage. The confirmation warns: "Critical services affected: <names> - expect a short outage for everyone." An Installer update does not interrupt users; only the service controls pause.