Software updates
The Resources tab of an Edge Gateway lists every Capture component on that gateway — CloudManager, Collector, Syncer, Analytics and any other linked software — with the version it is running and the versions available to it.
Available versions come from the Resource Library: a Software Update resource becomes available to a gateway once it is linked to that gateway, its fleet, or its project.
The versions table
| Column | Meaning |
|---|---|
| Item | The component. |
| Installed version | What the gateway reports it is running now. |
| Logs | The installation log of the last update, if there is one. |
| Status | Up to date, an update available, or the state of an update in progress. |
Use the Updates filter to show only the components that have a newer version available.
Two actions sit at the end of each row:
- The pencil opens the version list so you can change the installed version.
- The arrow opens the same list to download an installer instead of pushing it.
Changing a version needs manage rights on the gateway. Without them, only the download action is shown.
Push an update now
- Open the gateway, go to Resources, and select the pencil on the component's row.
- In the panel, select the version you want. The newest version is at the top; older versions are listed below it, so a rollback is the same action.
- The update is queued for the gateway immediately.
The gateway picks the update up on its next poll, downloads it and installs it. The row's Status follows along: Pushing update → Preloading update → Downloading update → Installing update → Update finished.
Installing an update restarts the service being updated. Collection or syncing stops for as long as that takes. This is the reason scheduling exists.
Schedule an update
Instead of pushing straight away, an update can be made to wait for a time window, a trigger, or both.
On the version's row, open the menu button next to the change button and select Schedule update. The dialog has two halves.
Scheduling is rolled out per environment. If the menu does not offer Schedule update, the feature is not enabled for yours yet — ask Capture support to switch it on.
Time window
| Field | Meaning |
|---|---|
| Update After | Do not install before this moment. |
| Update Before | Do not install after this moment. |
Each has its own checkbox; leave one off and that side of the window is open. Update Before must be in the future, and Update After must be earlier than Update Before.
While it is waiting, the gateway already downloads the update, so when the window opens the install starts immediately rather than beginning with a download.
If Update Before passes and the update has not been installed — because the gateway was offline, or because its trigger never became active — the update is cancelled and reported as failed. It is not installed late.
Trigger
The left-hand side of the dialog lists the triggers defined in this gateway's configuration, on the Triggers page. Select one and the update waits until that trigger is active.
This is how you install "when the machine is idle" rather than "at 3 a.m.": the trigger is a condition on the gateway's own data — a machine state, a mode, a production counter — so the update lands at a moment the process itself says is safe.
Combine the two and both conditions must hold: the update installs when the trigger becomes active and the moment is inside the window.
An update scheduled against a trigger the gateway's configuration does not contain can never fire. The gateway detects this, marks the update failed, and writes the reason into the installation log: "…is triggered by trigger '…', which is not defined in this device's collector configuration." Check the trigger still exists before scheduling, and re-push the update after fixing it.
A gateway whose configuration has no triggers shows No conditions/triggers available. Add a trigger on the configuration's Triggers page first.
While an update is waiting
The Status column shows what the gateway is waiting for:
| Status | Meaning |
|---|---|
| Pushing update | The update has been queued for the gateway. |
| Awaiting update trigger | The gateway has it and is waiting for the trigger and/or the window. |
| Preloading update / Downloading update | The package is being fetched. |
| Installing update | The install is running; the service will restart. |
| Update finished | Installed. |
| Cancellation pending | A cancel has been requested and not yet confirmed by the gateway. |
| Update canceled | The update will not be installed. |
While an update for a component is in flight, that component's version buttons are disabled, so a second update cannot be stacked on top of the first.
Cancel
A scheduled or in-progress update can be cancelled from the Status cell. Cancelling clears the schedule window and tells the gateway to stand down.
An update that has already finished, or already failed, cannot be cancelled — that result is final, and the cancel is refused rather than silently rewriting it.
Rolling out to more than one gateway
The scheduling dialog acts on the gateway you opened it from. To roll a version out more widely, link the Software Update resource to the fleet or project (see Resource details) so it becomes available everywhere, then push or schedule it per gateway.
Install and verify on one representative gateway before the rest, and roll out in batches. See Which version to use?.