Fix clw-scheduler-unreachable: Resolve OpenClaw scheduler connection failure

Mon, 13 Apr 2026 10:23:40 +0800

1. Symptoms

The clw-scheduler-unreachable error manifests in OpenClaw environments when the clw CLI or client libraries fail to establish a connection to the central scheduler service. Common indicators include:

CLI commands like clw submit job.yaml or clw status output:

Error: clw-scheduler-unreachable: Failed to connect to scheduler at clw-scheduler:8080 (dial tcp 127.0.0.1:8080: connect: connection refused)

Application logs show repeated connection attempts:

2024-10-05T12:34:56Z [ERROR] claw.client.SchedulerClient: Connection timeout to scheduler endpoint 'http://clw-scheduler.default.svc.cluster.local:8080/api/v1/health'

Jobs remain in PENDING state indefinitely without progression to RUNNING.
Dashboard (if accessible) reports “Scheduler offline” or shows zero active workers.

Kubernetes/Docker deployments exhibit pod restarts for scheduler components with events like:

Warning Unhealthy 10s kubelet Liveness probe failed: HTTP probe failed with statuscode: 503

This error disrupts job submission, monitoring, and scaling in OpenClaw clusters, often halting CI/CD pipelines or batch workloads. Network traces (e.g., via tcpdump) reveal SYN packets without ACK responses from the scheduler host.

Unreachable on ErrorVault — Developer Error Code Dictionary

Fix clw-scheduler-unreachable: Resolve OpenClaw scheduler connection failure

1. Symptoms