Routing on ErrorVault — Developer Error Code Dictionary

Fix clw-router-not-found: Router Component Not Registered in OpenClaw

Wed, 29 Jul 2026 22:20:04 +0800

1. Symptoms

When the clw-router-not-found error occurs during OpenClaw application execution, developers will observe specific indicators across different operation contexts. The error manifests primarily at application startup when the router initialization phase attempts to resolve registered router components.

Shell output during application boot:

[OpenClaw] ERROR: Router 'primary-router' not found in registry
[OpenClaw] CODE: clw-router-not-found
[OpenClaw] Hint: Verify router registration in openclaw.config.js

Runtime symptoms include:

Application fails to start with a non-zero exit code
Router-dependent services fail to initialize
HTTP routes become inaccessible even if defined elsewhere
Error logs show the specific router identifier that failed resolution
The application may hang at the routing initialization phase

Configuration validation failures:

Fix clw-router-denied: OpenClaw Router Request Denied Error

Sun, 26 Jul 2026 15:08:04 +0800

1. Symptoms

The clw-router-denied error occurs when the OpenClaw router middleware rejects an incoming request based on configured access control policies. This error manifests through several observable indicators that help distinguish it from other routing failures.

When the error is triggered, the client receives an HTTP 403 Forbidden response with a JSON payload containing the error code clw-router-denied. The response body typically includes a descriptive message explaining why the request was denied, along with the affected route identifier. In a command-line context, running OpenClaw CLI commands that interact with the router will display an error message prefixed with [ROUTER DENIED] followed by specific denial rationale such as missing credentials, blacklisted IP address, or invalid route permissions.

Fix clw-router-invalid: Router Configuration Schema Validation Failed

Sat, 11 Jul 2026 22:20:04 +0800

1. Symptoms

The clw-router-invalid error manifests during OpenClaw router initialization or when loading a route configuration file. You may encounter this error through several distinct indicators depending on when the validation occurs in your application’s lifecycle.

During Application Startup: When the router initializes at application boot, the validation failure produces output similar to the following:

[ClawRouter] ERROR: Router configuration validation failed
[ClawRouter] ERROR: clw-router-invalid - Schema validation error in route 'api/users'
[ClawRouter] DETAIL: Invalid field 'methods': expected array, received string
[ClawRouter] CONTEXT: Config file 'claw.routes.json' line 42, column 15

When Loading Routes Dynamically: If you load routes after startup using the dynamic route loading API, you might see: