Nextcloud Cronjob failure

[stray pulsar]

My last cronjob failed with:
Delivering to Nextcloud Talk requires target <roomToken>
How can I set that?

[zealous rain]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[civic quail]

Set the cron delivery target to the Nextcloud Talk room token.

For an existing cron job:

openclaw cron list
openclaw cron edit <job-id> --announce --channel nextcloud-talk --to "room:<roomToken>"
openclaw cron run <job-id>
openclaw cron runs --id <job-id> --limit 20

The roomToken is the Talk room token from the room URL, typically the part after /call/. The room: prefix is accepted and makes it explicit that this is a room target.

Also make sure the bot is enabled in that Nextcloud Talk room; otherwise delivery can resolve but Nextcloud may reject it. If the room is allowlisted in OpenClaw config, it should look like:

[civic quail]

{
  channels: {
    "nextcloud-talk": {
      rooms: {
        "<roomToken>": { requireMention: true }
      }
    }
  }
}

Docs: https://docs.openclaw.ai/automation/cron-jobs and https://docs.openclaw.ai/channels/nextcloud-talk

If it still fails after that, please share openclaw --version plus the output of openclaw cron show <job-id> with secrets redacted.

[stray pulsar]

openclaw cron list --json

  "delivery": {
    "mode": "announce",
    "channel": "nextcloud-talk",
    "to": "room:<ID>"
  },
  "lastDiagnosticSummary": "Error: Outbound not configured for channel: nextcloud-talk",
  "label": "announce -> nextcloud-talk:room:<ID>",
  "detail": "Unsupported channel: nextcloud-talk"

[civic quail]

That diagnostic means the room:<ID> part is no longer the problem. Cron can read the delivery config, but the running Gateway does not have outbound delivery registered for nextcloud-talk.

Please check these first:

openclaw --version
openclaw plugins list | grep -i nextcloud
openclaw plugins inspect nextcloud-talk
openclaw status --all

On current builds Nextcloud Talk should be bundled, but older/custom installs may need it installed/enabled:

openclaw plugins install @openclaw/nextcloud-talk
openclaw gateway restart

[civic quail]

If you are running from a source checkout instead of a packaged install, install the local bundled plugin path from the repo:

pnpm openclaw plugins install ./extensions/nextcloud-talk
pnpm openclaw gateway restart

Also check config if you use a plugin allowlist: plugins.allow must include nextcloud-talk, and plugins.entries.nextcloud-talk.enabled must not be false.

Docs: https://docs.openclaw.ai/channels/nextcloud-talk and https://docs.openclaw.ai/tools/plugin

[civic quail]

Thanks, that output is useful. Your Nextcloud Talk config/plugin is actually loaded and healthy, so this is not a missing bot secret or bad room token.

This looks like a 2026.5.20 outbound/cron routing bug: the plugin is loaded as a channel, but the cron delivery resolver still says Unsupported channel: nextcloud-talk. Current docs/source have changes in this area after 2026.5.20, so I’d update first:

openclaw update
openclaw doctor
openclaw gateway restart
openclaw --version
openclaw cron list --json
openclaw cron run <job-id>
openclaw cron runs --id <job-id> --limit 20

Docs: https://docs.openclaw.ai/install/updating

If openclaw update leaves you on 2026.5.20, check the updater output and your configured channel. If the same Unsupported channel: nextcloud-talk happens on the current release, that’s worth filing as a bug with your exact cron list --json, plugins inspect nextcloud-talk, and status --all output: https://github.com/openclaw/openclaw/issues

[stray pulsar]

Updating did it

[civic quail]

Glad that fixed it.

Please mark the solution so it gets indexed for the next person: right-click the solution message -> Apps -> ✅ Mark Solution.