Schedules
For AI Agents: the Markdown version of this page is at https://ankole.agentbull.com/en-US/docs/schedules/index.md. The documentation index is at https://ankole.agentbull.com/en-US/llms.txt.
Ankole provides two scheduling mechanisms side by side:
- Cron runs recurring tasks—such as a daily morning briefing, a weekly project summary, or a health check every 30 minutes.
- Checkback wakes the current conversation once after a delay so the Agent can follow up with its existing context.
Cron
Cron handles recurring work, triggered either on calendar times or at fixed intervals measured from an anchor timestamp.
Ask the Agent to create it
In everyday use, you do not need to open the Console. Simply message the Agent inside the conversation where you want results delivered, specifying what to do, when to run, and which timezone to follow.
The Agent creates the schedule and posts future runs back to that same conversation:
Create a schedule for every workday at 09:00. Summarize yesterday's progress,
current blockers, and today's follow-up items, then post the result in this
conversation. Use Asia/Shanghai. Run it once now so I can confirm the content
and delivery location.
Advanced: create a schedule in the Console
Before creating a schedule in the Console, exchange at least one message with the Agent in the target chat channel to verify that its routing rule can send and receive messages.
- Open Schedules in the Console.
- Select the Agent and the Session that owns the schedule; if it does not appear in the dropdown, enter its Session ID.
- Open the Cron tab and select New schedule.
- Choose the delivery routing rule and give the schedule a clear name.
- Enter the self-contained task, select the schedule kind, and configure its timing.
- Select the delivery conversation or enter its Ankole Conversation ID. Specify a provider thread ID only if every external-chat reply belongs in one topic or thread.
- Save the schedule and click Run now to confirm both the task output and the delivery destination before leaving it to run unattended.
Select a time rule
Use Cron (expression) for calendar schedules, such as 09:00 on weekdays. Expressions accept either five standard fields or six fields with leading seconds. Always specify a canonical IANA timezone such as Asia/Shanghai rather than an ambiguous offset like UTC+8:
0 9 * * 1-5
This expression fires at 09:00 Monday through Friday, evaluated in the timezone stored on the schedule rather than the browser’s or Worker’s local timezone.
Use Every (interval) for tasks that repeat on a fixed elapsed duration—such as every 30 minutes—when calendar alignment does not matter. Enter the interval and select seconds, minutes, hours, or days. The anchor timestamp defines the start of the interval grid.
Task and delivery
Each Agent-directed Cron rule runs in its own Session, separate from the conversation where it was created. Write a self-contained task that includes the context each run needs; the Cron Session does not inherit the originating Session’s transcript. The Agent still loads its persona and standing rules, so you do not need to copy its AGENTS.md or style instructions into the task.
Select the delivery conversation or enter its Ankole Conversation ID. For an external chat, also select its routing rule and optionally specify the provider thread ID. Test the destination with Run now.
Pause, resume, and remove
- Pause preserves the schedule configuration while halting future runs—ideal for holidays or maintenance windows.
- Resume recalculates the next fire time and re-enables scheduled runs.
- Run now triggers one immediate execution without shifting the regular schedule.
- Remove deletes the schedule permanently; choose Pause instead if you plan to turn it back on later.
Select any schedule to inspect its recent run history. If an expected report does not arrive in chat, check first whether the schedule fired, and then inspect the Agent turn and outbound message delivery.
Checkback
A Checkback is a one-time delayed follow-up that an Agent schedules mid-task—for example, “check the deployment status again in 30 minutes.” When the timer expires, Ankole wakes the originating conversation so the Agent can pick up right where it left off.
The Agent books a Checkback for a specific follow-up. The control plane dispatches the one-time wake-up when it is due; waiting for that deadline does not require repeated model turns.
In chat, tell the Agent when to check back, what condition to inspect, and whether to stay quiet when nothing has changed:
Check this deployment again in 30 minutes.
Tell me if it failed, became blocked, or changed state. Stay silent if nothing changed.
Open the Checkbacks tab in the Console to view pending reminders for a conversation, inspect their due times, reasons, and routing rules, or cancel any reminder that you do not need.
Applet Job schedules
For deterministic work, publish an Applet Action and create a Job in the Applet’s Automation panel. Add a schedule directly to that Job; no Agent session, task prompt, or chat destination is required. Configure Cron, a fixed interval, or a one-time date, choose the timezone, and supply the JSON payload the Action needs.
The panel supports editing, pausing, resuming, running once and deleting schedules. Inspect fire history and linked Runs, including failures and coalesced inputs. The Action reads event data through ctx.signal.data and stores durable progress in ctx.state. Personal schedules follow the Job owner’s authority; team schedules follow Page edit access.
Agent-created Cron and Checkback sources can also route to an Applet Job through their consumer binding. Keep a direct Agent consumer when every delivery needs judgment or conversation. See Automation Jobs and Worker CLI capabilities.
Common problems
- The schedule did not fire: Confirm that the schedule is active rather than paused, and verify its Cron expression, timezone, and computed next-run timestamp.
- The schedule fired, but nothing appeared in chat: Check the schedule’s run history, then verify that the signal routing rule, target channel, and Agent are all enabled.
- Runs happen several hours early or late: Replace any fixed UTC offset with the proper IANA timezone name, and check your deployment’s default timezone setting.
- Replies land in the wrong channel or thread: Update the delivery conversation or provider thread ID, then verify the fix with Run now.
- A Checkback never fired: Check the Checkbacks tab to see whether it is still pending, and verify both its due time and the routing rule for the originating conversation.
See Schedule troubleshooting for detailed error codes and recovery steps.