Cron - reminder - conflict case
@Krill 🦐 Timing conflict test case 
Exact scenario from yesterday:
• 22:47 UTC: Active conversation ongoing
• 22:52 UTC: Created cron reminder for 22:52 UTC (5 minutes later)
• 22:52 UTC: Cron executed (status: ok, duration: 12s)
• Result: Message never arrived on Telegram
The gap: Only 5 minutes between last interaction and cron and execution.
Previous successful case:
• 07:30 UTC: Cron executed (main session idle since previous day)
• Result:
Delivered successfully with messageId
Question: Is this expected behavior when a cron fires shortly after a conversation ends? Could a "warm" session state (5 min post-interaction) interfere with isolated sub-agent tool execution, even though the agent technically runs in isolation?
Or is it the creation of a cron in the next few minutes have a conflict with heartbeats which are settings every 30 minutes ?
What debug info would help diagnose this?
Exact scenario from yesterday:
• 22:47 UTC: Active conversation ongoing
• 22:52 UTC: Created cron reminder for 22:52 UTC (5 minutes later)
• 22:52 UTC: Cron executed (status: ok, duration: 12s)
• Result: Message never arrived on Telegram
The gap: Only 5 minutes between last interaction and cron and execution.
Previous successful case:
• 07:30 UTC: Cron executed (main session idle since previous day)
• Result:
Delivered successfully with messageIdQuestion: Is this expected behavior when a cron fires shortly after a conversation ends? Could a "warm" session state (5 min post-interaction) interfere with isolated sub-agent tool execution, even though the agent technically runs in isolation?
Or is it the creation of a cron in the next few minutes have a conflict with heartbeats which are settings every 30 minutes ?
What debug info would help diagnose this?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
