16 replies

cron job runs silently with no result/response

✅Solved

from cron job UI i can see job history says ‘ok’ but actually nothing happened, my job is to send a message to WhatsApp , just as simple as that

Solution

That log line is the giveaway:

-

durationMs: 29

durationMs: 29

is way too fast for “LLM runs + calls a skill + does network I/O”.
- The

summary

summary

is literally just your prompt text.

That pattern almost always means your cron job is a main-session “systemEvent” job (enqueue a note) — not an isolated “agentTurn” job (actually run the agent + tools). Main-session jobs can finish “ok” immediately because the scheduler only queued the event; the real work only happens when a heartbeat run picks it up (or when you set wake mode to run immediately).

So: not WhatsApp-specific at all — same issue for

dingtalk_send

dingtalk_send

or any other tool/skill.

What to check / fix

1) Check the job type in Cron UI
- If it says Session: main / Payload: system event → that explains “ok but nothing happened”.
- Change it to Session: isolated (agent turn). That runs the prompt directly in a fresh

cron:<jobId>

cron:<jobId>

run and can call skills.

2) If you must keep “main session”:
- Set wakeMode = now (or whatever the UI calls “wake immediately”)
- And make sure heartbeat is enabled and running (cron main-session jobs depend on heartbeat).

Jump to solution