cron

Scheduling automated tasks within a conversation involves creating timed actions using standard CRON syntax. The system uses command blocks to handle task creation, querying, and deletion with explicit confirmations for reliable execution.

Managing periodic reminders with CRON syntax requires creating a scheduled task within your conversation. The system enforces a one-task-per-conversation limit to prevent conflicts and uses explicit confirmations before modifying or deleting any existing reminders.

Creating multiple scheduled tasks in the same conversation is not supported. The system enforces a one-task-per-conversation limit to prevent conflicts and confusion, ensuring deterministic execution for your automated workflows.

Task deletion for scheduled workflows requires explicit user confirmation before any action is taken. The system queries and waits for results before deleting, using command blocks to ensure actions are deterministic and closed with explicit end markers.

You should avoid using conversation-based task scheduling if you need multiple timed tasks running simultaneously in one context. The one-task-per-conversation limitation makes it unsuitable for complex, multi-schedule workflows without segregating them across separate conversations.