openclaw - 💡(How to fix) Fix Bug: openclaw cron edit --tools fails with agentTurn payload (isolated sessions cannot get exec permission) [1 participants]

GatewayClientRequestError: invalid cron.update params: at /patch/payload: unexpected property 'message'; at /patch/payload: unexpected property 'toolsAllow'; at /patch/payload/kind: must be equal to constant; at /patch/payload: must match a schema in anyOf; must have required property 'jobId'; at root: unexpected property 'id'; must match a schema in anyOf

TL;DR

The openclaw cron edit command fails with an agentTurn payload when trying to set tools, likely due to schema validation errors.

Guidance

• The error message indicates that the --message and --tools flags together cause a schema error, suggesting that the combination of these flags is not supported.
• Try using the --message flag alone to auto-set the payload kind to agentTurn and session to isolated, and then edit the cron job separately to add tools.
• Consider using the workaround mentioned in the additional notes: use --session main with --system-event instead of isolated sessions.
• Verify that the isolated session's lack of exec permission is the root cause of the issue, and explore alternative solutions that do not require exec permission.

Example

No code snippet is provided as the issue does not require a code-level fix.

Notes

The issue is specific to the OpenClaw version 2026.4.1 and Darwin OS, and may not apply to other versions or environments. The lack of exec permission in isolated sessions and the inability to grant it via CLI may be a contributing factor to the issue.

Recommendation

Apply workaround: use --session main with --system-event instead of isolated sessions, as this is a known working alternative.