The leader keeps changing
Weik.io 2026.2The lead of a single-copy deployment moved to another agent three or more times in 15 minutes, usually because a copy restarts or loses the hub.
| Kind | Severity | Who sees it |
|---|---|---|
deployment- |
Warning | Everyone who can read the deployment |
The row’s figure gives the numbers in a few words, such as 4 changes in 15 min.
What it means#
The lead of a deployment that runs one copy at a time keeps moving between agents. Each move pauses the leader’s work for a moment, and a leader that keeps changing usually means a copy that restarts or loses its link to the hub.
What raises it#
The lead of one lock started on another agent than the lead before it three or more times in 15 minutes. Taking the lead again on the same agent doesn’t count, and a stopped deployment isn’t judged.
What to check#
See the state of each copy and how many times the lead changed in the last 24 hours:
$ weikio status <project>/<integration> --env <environment>Check the restarts of each copy and the leader changes of the last seven days:
$ weikio describe deployment <project>/<integration> --env <environment>Check the agents of the copies:
$ weikio get agents --env <environment>How to fix it#
When a copy keeps restarting, fix the cause its log gives. When an agent keeps going offline, check its site’s network link to the hub and the server’s memory and disk.