Connectors check for updates once an hour without being asked, so most of the time updating is something you watch rather than do.

Forcing it restarts the connector service on that machine, and the connector checks for a new version shortly after it comes back, usually within ten minutes. The machine itself is not restarted.

One limit matters more than any other on this page. A forced update only works while the connector is reachable.

Before you begin

Check the Status column for that machine. Anything other than ONLINE means the request will not land.

Expect a short gap in availability. The service stops and starts, so work in flight for that machine may fail.

Update it now

1. Open the fleet page and open the update option for that machine.
2. Read what version it is on and what is available.
3. Select the option to force the update check, which restarts the service.
4. Wait for the connector to reconnect.

The connector restarts within seconds and reconnects within about half a minute. The version on the row changes only after it has checked and updated, which takes longer.

Good to know

Several outdated connectors can be updated together rather than one at a time, which is the better route when a version goes out across a fleet. That route covers only connectors that are reachable and new enough to update themselves.

The hourly check means an untouched connector catches up on its own. Forcing it is for when you need the new version now.

Older connectors do not offer the forced check at all. Where the dialog shows a command to run instead of a button, that machine has to be updated with the command.

Verify it worked

Refresh the page rather than watching. The list does not update on its own.

The status should return to ONLINE within about a minute. The version takes longer, so give it fifteen minutes before concluding the update did not take.

If something doesn’t look right

If the connector does not come back, treat it as an offline connector rather than a failed update. The machine is the place to look.

If the version is unchanged after fifteen minutes, that connector is probably too old to update itself. Use the command shown in the update dialog, on that machine.

If the machine was offline when you pressed it, the request was lost. Repeat it once the machine is back.

To report a failure, open a support conversation from the Help drawer with the client, the machine, and the version it is stuck on.

FAQ

Q: Does this restart the server?

A: No. Only the connector service on it.

Q: Do I need to do this at all?

A: Usually not. Connectors check hourly by themselves.

Q: Can I update several at once?

A: Yes, and that is the better route for a fleet-wide version change. It skips anything unreachable or too old.