What causes the "null to object" error in v2026.3.1?

A regression in the Vertex provider where it fails to handle empty response metadata in embedded execution modes.

Which OpenClaw versions are affected?

Primarily v2026.3.1. Older versions like v2026.2.26 are stable.

How do I fix it quickly?

Downgrade to v2026.2.26 or apply the environment variable fix to skip metadata processing.

Fix Vertex "null to object" Crash (v2026.3.1)

Critical Regression in v2026.3.1

This is a confirmed regression in the latest OpenClaw update. It specifically breaks Vertex AI when used in embedded mode (Telegram bots, Discord group replies, and scheduled cron jobs).

If your Telegram bot or cron jobs stopped working after the March 2026 update, showing a TypeError: Cannot convert undefined or null to object, you are hitting a bug in how OpenClaw parses Vertex metadata.

Confirmed pattern: openclaw/openclaw#32245 (v2026.3.1, Telegram + cron embedded runs).

Next Step

Fix now, then reduce repeat incidents

If this issue keeps coming back, validate your setup in Doctor first, then harden your config.

Open Doctor Harden Config

Need proactive alerts? Join Monitor early access.

Quick Solutions

Option 1: Version Downgrade (Recommended) Option 2: Config Hotfix Option 3: Environment Variable bypass Check for Official Patch

Symptoms

embedded run agent end ... isError=true error=Cannot convert undefined or null to object

TypeError: Cannot convert undefined or null to object at VertexProvider.parseMetadata

Cron job <id> failed: Cannot convert undefined or null to object

Vertex embedded runs fail with Cannot convert undefined or null to object on v2026.3.1 (Telegram + cron)

Fix 1: Downgrade to v2026.2.26

The most reliable fix until v2026.3.2 is released is to roll back to the previous stable version. This version does not contain the breaking Vertex parser changes.

Reinstall stable version

npm install -g [email protected]

Fix 2: Disable Vertex Usage Metadata

The crash occurs when OpenClaw tries to calculate token costs for Vertex. You can temporarily bypass this by disabling usage tracking in your provider config.

Update openclaw.json

"providers": {
  "vertex": {
    "module": "vertex",
    "config": {
      "project": "your-project",
      "skipMetadata": true  // Add this line
    }
  }
}

Fix 3: Global Environment Override

If you cannot easily edit your config file (e.g., in a Docker environment), you can set a global flag to skip the faulty parsing logic.

Set environment variable

export OPENCLAW_VERTEX_SKIP_METADATA=1\nopenclaw gateway restart

Check for Official Patch

The OpenClaw team is tracking this in Issue #32245. Run the following command to see if a newer, fixed version is available:

Check for updates

npm view openclaw version\n# If version > 2026.3.1, run:\nnpm install -g openclaw@latest

Verify the Fix

After applying the fix, trigger a manual cron run or send a message to your Telegram bot to ensure the crash is gone.

openclaw cron run --all

Did this guide solve your problem?