Resource-Limit on ErrorVault — Developer Error Code Dictionary

Fix clw-gpu-limit-exceeded: GPU Resource Quota Exceeded in OpenClaw

Fri, 07 Aug 2026 22:20:04 +0800

1. Symptoms

The clw-gpu-limit-exceeded error manifests when a workload attempts to utilize more GPU compute resources than are available within your OpenClaw account quota. This error typically surfaces during job submission, container deployment, or when scaling GPU-accelerated workloads.

Shell Output Indicators

When attempting to launch a GPU-accelerated workload, you may encounter output similar to the following:

$ clw job submit --gpus 4 --image tensorflow:latest --command "python train.py"
Error: clw-gpu-limit-exceeded
Message: Requested 4 GPUs but only 2 available in quota. Current usage: 2/2 GPUs allocated.

Quota Details:
  - Total GPU quota: 2
  - Currently in use: 2
  - Requested: 4
  - Available: 0

Suggestion: Reduce GPU request, wait for running jobs to complete, or request a quota increase via the OpenClaw console.

Additional Symptoms

Beyond the command-line output, you may observe the following indicators that suggest a GPU limit issue:

Fix clw-sandbox-exhausted: OpenClaw Sandbox Resource Limit Exceeded

Sun, 02 Aug 2026 15:08:04 +0800

1. Symptoms

When the clw-sandbox-exhausted error occurs during OpenClaw execution, users encounter several distinct indicators that signal resource depletion within the sandbox environment. The error manifests immediately after initiating a sandboxed operation, typically during code execution, test runs, or build processes that require isolated runtime environments.

The primary symptom presents as an explicit error message displayed in the terminal output:

[ERROR] clw-sandbox-exhausted: Sandbox resource limits have been reached
Sandbox execution terminated. Current usage exceeds allocated quota.

Beyond the primary error message, secondary symptoms often accompany this failure. Users frequently report that the process terminates abruptly without producing expected output files, logs, or artifacts. The exit code returned to the shell is typically non-zero, often 137 which indicates the process was killed by the system due to resource constraints. In containerized environments, the container may enter a restart loop or remain in a terminated state.

Fix clw-worker-exhausted: Worker Process Memory Limit Exceeded

Wed, 29 Jul 2026 07:56:04 +0800

1. Symptoms

When the clw-worker-exhausted error manifests in your OpenClaw environment, you will observe several distinct indicators that point toward worker resource depletion. The most prominent symptom is a sudden cessation of task processing from a specific worker node. Tasks that were previously being executed will remain in a pending or in-progress state without completion.

In the command-line interface, running clawctl status or clawctl worker list typically reveals workers with an EXHAUSTED status. The output may include additional diagnostic information such as the memory threshold that was breached and the current memory consumption of the affected worker process.