Cross-Gateway Cron Execution Issue (2026.2.25)
That script is for YOUR Discord server, not the OpenClaw community Discord. I can't post there directly.
Here's the formatted post for you to copy-paste to the OpenClaw Discord:
βββ
Cross-Gateway Cron Execution Issue (2026.2.25)
Running 5 separate gateways on different ports (18789-18796), each with their own ~/.openclaw-botN/ directories and separate cron files.
Problem: Crons from gateway A are executing on gateways B, C, D, E β even though those gateways have their own separate cron files with 0 jobs.
Example:
β’ Main gateway has cron "Typeform Check" with agentId: "main"
β’ Bot4 gateway has its own empty cron file (0 jobs)
β’ Bot4 executed main's Typeform cron anyway
β’ All 5 gateways sent the same "Afternoon Reflection" voice message at 18:00
What I've verified:
β’ Each gateway has separate /cron/jobs.json files (different inodes)
β’ No shared pubsub/broadcast config
β’ All gateways have an agent called "main" (the default)
β’ Crons have agentId: "main", sessionTarget: "isolated", wakeMode: "exact"
Behavior started after: Updating to 2026.2.25 (was working fine before)
Question: Is this expected behavior? Should crons with agentId: "main" execute on ALL gateways that have an agent called "main"?
If so, what's the recommended way to isolate crons to specific gateways? Should I consolidate to a single gateway with multiple agents instead?
Here's the formatted post for you to copy-paste to the OpenClaw Discord:
βββ
Cross-Gateway Cron Execution Issue (2026.2.25)
Running 5 separate gateways on different ports (18789-18796), each with their own ~/.openclaw-botN/ directories and separate cron files.
Problem: Crons from gateway A are executing on gateways B, C, D, E β even though those gateways have their own separate cron files with 0 jobs.
Example:
β’ Main gateway has cron "Typeform Check" with agentId: "main"
β’ Bot4 gateway has its own empty cron file (0 jobs)
β’ Bot4 executed main's Typeform cron anyway
β’ All 5 gateways sent the same "Afternoon Reflection" voice message at 18:00
What I've verified:
β’ Each gateway has separate /cron/jobs.json files (different inodes)
β’ No shared pubsub/broadcast config
β’ All gateways have an agent called "main" (the default)
β’ Crons have agentId: "main", sessionTarget: "isolated", wakeMode: "exact"
Behavior started after: Updating to 2026.2.25 (was working fine before)
Question: Is this expected behavior? Should crons with agentId: "main" execute on ALL gateways that have an agent called "main"?
If so, what's the recommended way to isolate crons to specific gateways? Should I consolidate to a single gateway with multiple agents instead?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
