Harness "No eligible delegate ... available" in CI

Harness assigns each task to a delegate that can run it. "No eligible delegate" means no connected delegate matched the task: either none are connected, none carry the required selector, or none can reach the target.

What this error means

A pipeline step fails with "No eligible delegate(s) could perform the required capabilities" or "No delegates could reach resource". The step never runs because nothing was assigned.

No eligible delegates available to execute the task.
Following delegate(s) failed to meet selection criteria:
delegate-prod : missing selector [k8s-prod]

Common causes

No delegate carries the required selector

The connector/step requires a selector (for example k8s-prod) that no connected delegate has, so none is eligible.

No delegate can reach the target resource

Delegates are connected but none has network reachability to the cluster, registry, or git host the task needs.

How to fix it

Add the matching selector to a reachable delegate

1. Check which selector the connector/step requires.
2. Tag a delegate that can reach the target with that selector.
3. Confirm the delegate is Connected, then re-run the pipeline.

# In delegate YAML/tags, add the required tag
tags:
  - k8s-prod

Place a delegate with network access to the target

Deploy or move a delegate into a network that can reach the cluster/registry/git host the task requires.

How to prevent it

• Keep delegate selectors aligned with connector requirements.
• Run delegates where they can reach every target they serve.
• Alert when delegate count for a required selector drops to zero.

Related guides