Environment
- Product: AutoClaw (z.ai) macOS desktop app
- Version: 2.0.2 (
com.zhipuai.autoclaw2)
- Platform: macOS (darwin, arm64)
- Credit: Reported by community user eskibars on Discord
Bug Summary
Every invocation of the schedule_task tool in AutoClaw fails validation and is rejected by the host before execution, making the task scheduling feature completely unusable.
Error Output
{
"status": "rejected",
"code": "[{\"origin\":\"string\",\"code\":\"invalid_format\",\"format\":\"uuid\",\"pattern\":\"/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$/\",\"path\":[\"commandId\"],\"message\":\"Invalid UUID\"}]"
}
Root Cause Analysis
commandId is not present in the tool's public schema (label, schedule, action, policies). The caller does not supply commandId.
- The failing value is generated internally on the host side.
- At schema validation time,
commandId appears to be undefined, empty, or unpopulated before the UUID regex validator runs.
Steps to Reproduce
Call schedule_task with a minimal valid payload:
{
"label": "test",
"schedule": { "kind": "at", "delayMs": 300000 },
"action": { "kind": "agent_prompt", "prompt": "Reply READY." },
"policies": {
"misfire": { "policy": "run_once", "graceMs": 3600000 },
"overlap": "skip",
"retry": { "maxAttempts": 1, "backoffMs": 600000 }
}
}
Expected: Task created and scheduled.
Actual: Rejected immediately with "Invalid UUID" on commandId.
Impact
Recurring and delayed agent workflows cannot run. Every scheduled task fails before instantiation.
Suggested Fix
Ensure commandId is assigned a valid UUID string before the schema validation layer executes on the host.
Environment
com.zhipuai.autoclaw2)Bug Summary
Every invocation of the
schedule_tasktool in AutoClaw fails validation and is rejected by the host before execution, making the task scheduling feature completely unusable.Error Output
{ "status": "rejected", "code": "[{\"origin\":\"string\",\"code\":\"invalid_format\",\"format\":\"uuid\",\"pattern\":\"/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$/\",\"path\":[\"commandId\"],\"message\":\"Invalid UUID\"}]" }Root Cause Analysis
commandIdis not present in the tool's public schema (label,schedule,action,policies). The caller does not supplycommandId.commandIdappears to be undefined, empty, or unpopulated before the UUID regex validator runs.Steps to Reproduce
Call
schedule_taskwith a minimal valid payload:{ "label": "test", "schedule": { "kind": "at", "delayMs": 300000 }, "action": { "kind": "agent_prompt", "prompt": "Reply READY." }, "policies": { "misfire": { "policy": "run_once", "graceMs": 3600000 }, "overlap": "skip", "retry": { "maxAttempts": 1, "backoffMs": 600000 } } }Expected: Task created and scheduled.
Actual: Rejected immediately with
"Invalid UUID"oncommandId.Impact
Recurring and delayed agent workflows cannot run. Every scheduled task fails before instantiation.
Suggested Fix
Ensure
commandIdis assigned a valid UUID string before the schema validation layer executes on the host.