Update the platform
Updated
Apply a newer Zulo platform image, or Zulo's own models, to one environment. The stand is snapshotted first. If it does not come back healthy, it is moved back.
Note
Production tells you to update a Test environment first and run your tests there. Packages marked Ready for production were proven on the current platform; after a Production platform update, each is installed on Test again on the new release before its next Release.
The portal is lcp.getzulo.com. Its buttons are in English.
How to#
To update, sign in at lcp.getzulo.com and open the tenant. Open Environments, then the stand (start with Test). Under Updates from Zulo:
Platform shows what it runs and the newest release. If Production has an update and no other environment runs that release yet, the page says so. On Test, press Update to that version. The stand is snapshotted and restarted; if it does not come back healthy it is moved back.
Zulo's models lists models that are behind. Press Install Zulo's model updates. That installs those models and what they need while the stand runs. A snapshot is taken first.
When Test is healthy and its tests are green (Tests on the same environment: Run tests — a run rolls back what it writes), open Production and update it the same way.
Logs on the environment (newest first) stay readable if the stand is stopped.
Example
Test
acme-testruns2026.0.800. Newest is2026.0.823.Update to 2026.0.823 on Test. Run tests. Then the same Update to on Production.
Tip
Back up now if you want a named copy on top of the snapshot the update takes itself.
If the command refuses#
| What you see | What to do |
|---|---|
| None of the tenant's other environments runs the newest yet | Update Test first, then come back to Production. |
| Update is missing and a muted why | Read that line — often a job is already running, or the plan does not allow it. |
| The stand comes back on the old version | The new image did not become healthy. Read Logs, fix, try Test again. |
See also