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 isn't done.
| 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, and no copy leads it. Every copy stands by, so the work the leader does, such as polling a folder or running a schedule, isn’t done.
What raises it#
A copy is online and running and competes for the lock, but no copy has led it for more than a minute. The problem applies to the deployment’s own lock and to each master: lock a copy reports.
What to check#
See which copy leads, which stand by 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#
The platform’s lock is kept on the hub, 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, then restart the deployment if no copy takes over:
$ weikio restart <project>/<integration> --env <environment>