16d • General discussion
Cron commands fail with “pairing required” even though gateway is running and status works
I was trying to set up a simple daily reminder using openclaw cron, but all cron commands failed with:
gateway connect failed: GatewayClientRequestError: pairing required
What I tested:
• openclaw status worked
• openclaw gateway status showed the gateway running and RPC probe ok
• openclaw cron status, openclaw cron list, and openclaw cron add ... all failed with pairing required
• ran openclaw doctor
• ran openclaw doctor --fix
• regenerated gateway token through openclaw configure
• restarted gateway with openclaw gateway restart
At one point the dashboard/config flow also showed:
unauthorized: gateway token mismatch
After token regeneration + restart, the mismatch cleared, but cron still failed with pairing required.
This seems like a broken local auth/pairing state for cron specifically, with no clear recovery path. The UX is especially confusing because normal status checks work while cron remains unusable.
2
0 comments
Cron commands fail with “pairing required” even though gateway is running and status works
skool.com/openclawusers
Free community for OpenClaw users to install, build, break, fix and share wild AI agent ideas together.
Leaderboard (30-day)
1
+21
2
+5
3
+5
4
+4
5
+3
Powered by