Skip to content
Weik.ioDocs
2026.2
Try Weik.io

The leader keeps changing

Weik.io 2026.2

The lead of a single-copy deployment moved to another agent three or more times in 15 minutes, usually because a copy restarts or can't reach the hub. Video

Watch: One copy at a time, 3:01

The video runs one copy of an integration at a time across two agents with singleton: true.

On this page
Kind Severity Who sees it
deployment-leader-changing Warning Everyone who can read the deployment

Its row in the problem list has a figure 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.

What raises it#

The lead of one of the deployment’s locks moved to a different agent three or more times in 15 minutes. Taking the lead again on the same agent doesn’t count. A stopped deployment doesn’t raise the problem.

What to check#

See the state of each copy and how many times the lead changed in the last 24 hours:

Terminal
$ weikio status <project>/<integration> --env <environment>

Check the restarts of each copy and the leader changes of the last seven days:

Terminal
$ weikio describe deployment <project>/<integration> --env <environment>

Check the agents of the copies:

Terminal
$ weikio get agents --env <environment>

How to fix it#

When a copy keeps restarting, fix the cause in its log. When an agent keeps going offline, check its network link to the hub and the server’s memory and disk.

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo