Cloudwatch on ErrorVault — Developer Error Code Dictionary

Fix clw-worker-disconnected: Worker Connection Lost in OpenClaw

Thu, 06 Aug 2026 15:08:04 +0800

1. Symptoms

The clw-worker-disconnected error manifests when the OpenClaw worker process loses its connection to the CloudWatch Logs service or the central coordination server. Users typically encounter this error during active log streaming operations or when attempting to initiate a new worker instance.

Typical Error Output:

[ERROR] clw-worker-disconnected: Worker instance worker-abc123 has been disconnected from the CloudWatch endpoint
[ERROR] Failed to send log batch: connection reset by peer
[WARN] Retrying connection in 5 seconds...
[FATAL] Maximum reconnection attempts (3) exceeded

Observable Symptoms:

Fix clw-llm-oom: OpenClaw LLM Context Overflow Error

Fri, 31 Jul 2026 07:56:04 +0800

1. Symptoms

The clw-llm-oom error manifests when OpenClaw attempts to process large volumes of CloudWatch log data through its LLM integration pipeline. When this error occurs, users typically observe the following indicators:

Shell Output:

[ERROR] OpenClaw LLM processing failed: clw-llm-oom
[ERROR] Context window exhausted. The log batch exceeds the model's maximum token limit.
[ERROR] Attempted to process 47,832 tokens against a 8,192 token context window.

Behavioral Symptoms:

The CLI command terminates immediately after initiating LLM analysis
Processing jobs fail consistently regardless of retry attempts
The error appears even when processing logs that previously succeeded
Memory usage on the host system spikes before the error occurs
The error message includes token count statistics showing the excess

Additional Console Messages:

Fix clw-agent-exhausted: CloudWatch Agent Resource Pool Exhaustion

Fri, 31 Jul 2026 00:44:04 +0800

1. Symptoms

The clw-agent-exhausted error manifests when the OpenClaw CloudWatch agent reaches its maximum concurrent log processing capacity. This error typically appears during high-volume log ingestion scenarios or when the agent is configured with insufficient worker threads to handle the incoming log stream volume.

Common indicators include:

Error message: clw-agent-exhausted: Maximum concurrent requests exceeded for CloudWatch Logs agent
Log entries showing partial log delivery or dropped log lines
CloudWatch agent process consuming excessive CPU and memory
Intermittent log gaps in CloudWatch Logs console despite logs being generated
API throttling responses from the CloudWatch Logs endpoint (ThrottlingException)
Agent status showing “running” but with degraded throughput performance

Shell output examples: