Summary

today update
from 2026.12.13 to 2026.12.14
then to 2026.12.15
then the cron is not working

Description:

After running openclaw configure to re-pair the device and starting the gateway with openclaw gateway, the cron tool fails with the following error:

gateway closed (1008): unauthorized: device token mismatch (rotate/reissue device token)
Gateway target: ws://127.0.0.1:18789

Steps to reproduce:

1. Run openclaw configure to pair device
2. Run openclaw gateway
3. Try to use cron tool - it fails with "unauthorized: device token mismatch"

Environment:

• OpenClaw version: 2026.2.15
• OS: ubuntu 24.04(VPS)

What I've tried:

• Deleted ~/.openclaw/devices/ multiple times
• Re-paired device multiple times
• The token in ~/.openclaw/identity/device-auth.json matches ~/.openclaw/devices/paired.json
• But gateway still rejects the connection

This seems like a caching or state synchronization bug in the gateway.

Steps to reproduce

Steps to reproduce:

1. Run openclaw configure to pair device
2. Run openclaw gateway
3. Try to use cron tool (e.g., cron list)

Expected result: Cron tool should work normally
Actual result: Error - "gateway closed (1008): unauthorized: device token mismatch (rotate/reissue device token)"

Expected behavior

Expected behavior:
Cron tool should work normally after device re-pairing. The tool should be able to list, add, run, and manage cron jobs without authentication errors.

Actual behavior

Actual behavior:
Error message:
"gateway closed (1008): unauthorized: device token mismatch (rotate/reissue device token)
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: .openclaw/openclaw.json
Bind: loopback"

Additional notes:

• ~/.openclaw/identity/device-auth.json and ~/.openclaw/devices/paired.json contain matching tokens
• Message tool works fine (Telegram messaging is functional)
• Only cron tool fails with token mismatch error
• This prevents managing cron jobs (list, add, run, etc.)

OpenClaw version

2026.2.15

Operating system

ubuntu 24.04

Install method

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response