Openclaw runtime cron jobs ======> push?

Bugs / Site Issues
1

I am deployed to Telegram. When I schedule a cron job, it runs, but doesn"t deliver it to the chat.

Here is the self analysis:

Here’s a technical summary you can share with the Pickaxe/OpenClaw developers:

The cron scheduler is executing correctly, but announcement delivery back into the active webchat thread appears broken or unsupported.

Observed behavior:

• A recurring cron job was created successfully with:
• payload.kind = "agentTurn"
• sessionTarget = "current"
• delivery.mode = "announce"
• delivery.channel = "webchat"
• delivery.to = "current"
• The job runs on schedule and manual triggering also works.
• Run history shows each invocation finishing successfully with:
• status: "ok"
• valid generated summary
• valid sessionKey for the cron run session
• However, the resulting message does not appear in the user-visible webchat thread.
• deliveryStatus is consistently reported as "unknown" rather than a confirmed delivered/failed state.

Concrete evidence:

• Cron job state shows:
• lastRunStatus: "ok"
• consecutiveErrors: 0
• nextRunAtMs advancing normally
• cron runs returns completed entries with generated output summaries, meaning:
• scheduler fired
• agent turn executed
• model completed
• The missing piece is the final delivery/announce path into webchat.

Likely failure domain:

• Not scheduler timing
• Not agent execution
• Not tool availability inside the cron run
• Most likely one of:

  1. announce delivery to webchat + to=current is not implemented correctly
  2. cron-run session output is generated but not bridged back to the parent interactive thread
  3. webchat does not support this delivery mode, but the system reports unknown instead of a clear unsupported/failed status
  4. sessionTarget=current resolves for execution, but not for outbound delivery routing

Repro steps:

  1. Create a cron job with:
    • recurring or one-shot schedule
    • payload.kind: "agentTurn"
    • sessionTarget: "current"
    • delivery.mode: "announce"
    • delivery.channel: "webchat"
    • delivery.to: "current"
  2. Let it run or force-run it with cron run
  3. Check:
    • cron runs shows status: ok
    • summary text exists
    • no visible message appears in the current webchat conversation
    • deliveryStatus remains unknown

Expected behavior:

• Either:
• the generated cron result should appear visibly in the current webchat thread, or
• the platform should return an explicit delivery failure/unsupported status

Actual behavior:

• Cron run completes successfully
• No visible user-facing delivery in webchat
• Delivery telemetry is ambiguous (unknown)

Suggested fixes:

• Add explicit delivery confirmation/failure states for webchat announce delivery
• Verify routing for delivery.channel=webchat and to=current
• Verify whether cron-run outputs are allowed to post into the originating live thread
• If unsupported by design, reject job creation up front or mark delivery as unsupported rather than unknown

Short version:

The cron engine and agent execution path work; the bug is in the final delivery bridge from cron-run output to the active webchat conversation.

Telegram and Discord deployments are live ⚡️
2

thanks for the detailed report Doug ! we’ll take a look and get back to ya ASAP

3

updating here: should be all set on crons in Telegram ! @dougfresh

4

Carson… thank you !!!
I know you must have fixed it when I woke up to 70 messages from my pickaxe on Telegram :slight_smile:
I had set a cron for ever 10 min to test it! lol!