A single-copy deployment has no leader
Weik.io 2026.2A deployment that runs one copy at a time has had no leader for more than a minute, so work such as polling a folder stops. 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.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
deployment- |
Error | Everyone who can read the deployment |
What it means#
The deployment runs one copy at a time, with singleton or Camel’s master: component, but no copy leads it. Every copy stands by, so the work the leader does, such as polling a folder or running a schedule, stops.
What raises it#
At least one copy runs on an online agent and competes for a lock, but no copy has led that lock for more than a minute. The lock can be the deployment’s own or one that its routes take with master:. The row’s title lists the routes’ locks that no copy leads. When no copy leads the deployment’s own lock, the title lists no lock.
What to check#
See which copy leads and how many times the lead changed in the last 24 hours:
$ weikio status <project>/<integration> --env <environment>Read the copies’ log lines about the lock:
$ weikio logs <project>/<integration> --env <environment> --since 15m --query lockHow to fix it#
Weik.io keeps the lock, so a copy that can’t reach the hub can’t take the lead. Check that the agents of the copies are online and can reach the hub. If no copy takes over, restart the deployment:
$ weikio restart <project>/<integration> --env <environment>