Support
Update Vector OS and connectors
Check eligibility, finish uncertain work and verify the new app or connector after a safe restart.
Before you begin
- The installed app/plugin/host versions and current release notes for the eligible replacement.
- Access to the original workspace, update/connector lifecycle journals and a supported compatible recovery path.
- A safe boundary with no unresolved native work or active operation blocking apply/removal.
Follow the steps
Read current and offered versions
Check the installed version in About/Help or Updates. Read the offered release identity, compatibility, restrictions and withdrawal status.
Checkpoint: You know the exact current and eligible target versions. Cached or historical bytes alone do not establish eligibility.
Review the intended change
For an app update, read data/migration and restart requirements. For a connector, review its exact host/runtime lane, registration scope and affected instances.
Checkpoint: The plan explains what changes and what must remain available for recovery.
Finish or reconcile active work
Stop new admission at the safe boundary, finish or reconcile affected operations and save important host work. Close affected host instances normally when required.
Checkpoint: No unresolved write or busy host is bypassed to apply the update.
Stage only verified eligible bytes
Use the supported download/staging flow. Check publisher, signature/hash, available space and metadata freshness. Keep the current version until replacement verification.
Checkpoint: The replacement is verified and ready; downloaded is not yet applied.
Apply through the supported restart
Follow Restart/apply only when the update plan is eligible, its backup/journal exists and the safe boundary is confirmed. Do not overwrite a busy runtime or force an unsupported rollback.
Checkpoint: The update/migration has a known completed or recoverable state.
Read back after restart
Check the installed app/plugin version. Reconnect the exact host and selected document and require a fresh handshake for a connector update.
Checkpoint: The new version/registration and compatibility are verified. A package-manager exit code or launched process is not native acceptance.
Check the result
- The intended eligible app/plugin version is read back after the required restart, with preserved workspace and a fresh connector handshake when applicable.
- Downloading, registration, launch and verified native behavior remain separate states.
If something goes wrong
Signature/hash fails, metadata expired or the release is withdrawn.
Do not apply. Keep the installed safe state and ask for an eligible replacement; never bypass protections or substitute withdrawn cached bytes.
Resume from: Eligible verified update identity.
A native operation remains unknown or a host is busy.
Defer apply. Reconcile the original operation and close affected hosts normally at a safe boundary.
Resume from: Known native state and safe host exit.
Apply/migration is interrupted or registration response is lost.
Preserve backup, prior eligible receipt/bytes and the lifecycle journal. Inspect actual inventory/data state before supported resume or compatible rollback.
Resume from: Known recoverable update phase.
The updated host starts without a valid handshake.
Report repair required and inspect version/runtime/registration drift. Do not claim Connected or blindly delete add-in files.
Resume from: Verified registration then authenticated handshake.
Need help?
Include your step and this reference.
Vector OS guide: /tutorials/update-vector
Guide updates
Update Vector and connectors
Revision 2c23ebe5647b7454bd1524129d41d9bc0704f9e719fb491405641a05a397867a ·