openclaw - 💡(How to fix) Fix [Bug]: Discord proactive cron reminder delivery fails with "Unknown Channel" while Telegram works [2 comments, 3 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Discord proactive cron reminder delivery fails with Error: Unknown Channel in isolated cron runs, while Telegram reminder delivery and reactive Discord DM chat work in the same environment.

Steps to reproduce

1. Create a one-shot Discord cron reminder with explicit DM target: openclaw cron add --name "Discord DM reminder test" --at "2026-05-01T06:19:17Z" --session isolated --message "Send a short Discord DM reminder to Uragon: target-format test." --announce --channel discord --to "user:713120455187234836" --delete-after-run --json
2. Wait for the cron run to execute.
3. Inspect the run result with: openclaw cron runs --id 62b75f3b-5171-4859-a74f-612693a6be98 --limit 20
4. Observe that the run finishes with Error: Unknown Channel.

Expected behavior

The isolated cron run should deliver the proactive Discord DM successfully to user:713120455187234836, or return a Discord-specific DM send error if Discord rejects the DM.

Actual behavior

The isolated cron run finishes with Error: Unknown Channel and deliveryStatus: unknown, and no Discord DM is delivered.

OpenClaw version

2026.4.15

Operating system

Ubuntu 24.04 Linux 6.17.0-22-generic (x64)

Install method

NOT_ENOUGH_INFO

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> openai-codex

Additional provider/model setup details

Channels enabled during testing: Telegram and Discord. Telegram cron reminder delivery succeeded in the same environment. Discord reactive DM chat succeeded in the same environment. The failing path was isolated cron delivery with --announce --channel discord --to "user:713120455187234836".

Logs, screenshots, and evidence

Observed successful Telegram cron delivery in the same environment:
- Job id: 9cc429ea-fa21-40f1-8afe-ae77be2d1e79
- Result: delivered
- Summary: "Telegram reminder for Rey: test reminder from Reggie."

Observed failed Discord cron deliveries in the same environment:
- Job id: 3174290e-ff62-4770-bbca-0a76f727d43b
- Job id: 62b75f3b-5171-4859-a74f-612693a6be98
- Result: error
- Error: "Error: Unknown Channel"
- deliveryStatus: unknown

Observed job config for failed Discord runs:
- delivery.channel = "discord"
- delivery.to = "user:713120455187234836"

Observed that reactive Discord DM chat still worked while proactive cron delivery failed.

Impact and severity

Affected: OpenClaw users attempting proactive Discord DM reminder delivery from isolated cron jobs Severity: Medium, blocks proactive Discord reminder workflow Frequency: Always in the observed Discord cron reminder tests (2/2 failed), while Telegram cron reminder delivery succeeded (1/1) Consequence: Scheduled Discord reminders are not delivered; users must use another channel such as Telegram as a workaround

Additional information

This appears specific to isolated cron outbound delivery for Discord. The scheduler itself worked, Telegram reminder delivery worked, and Discord reactive DM chat worked in the same environment. That suggests the failure is likely in the Discord outbound/plugin resolution path for cron delivery rather than in cron scheduling itself.