Reference

Why is my update blocked or waiting?

The update safety gate found genuinely running work. Unsafe work blocks; re-runnable work drains.

ReadyCurrentupdatessafety-gateoperations

The Short Answer

Before an update runs, Sendense checks for operations that are genuinely running at that moment, using live runtime evidence. Work that would be unsafe to interrupt blocks the update until it finishes. Re-runnable work - an in-flight backup, replication sync, or restore - produces a warning instead, and choosing update-when-ready starts the update once that work completes.

What To Do

Let blocking work finish, or plan the update inside a maintenance window.
Use update-when-ready to queue the update behind re-runnable work instead of watching for a quiet moment.
If an installation is interrupted mid-flight, rollback behavior is intended to protect the update process - review status before retrying.