Skip to content

Schedules

Ask Cora in a mission to do something later, or again and again, and she sets up a schedule. When it is due she wakes, does the work and posts the result in the mission, as she would if you had just asked.

The examples on this page follow an invented bike shop, Kestrel Cycles, and its mission “Weekend rides”.

Write to Cora in the mission, in your own words. Say what you want and when:

  • “@Cora every weekday at 9 am, post a summary of yesterday’s open tasks.”
  • “@Cora at 4 pm on Friday, remind us to send the ride notes.”
  • “@Cora every 2 hours, check the bookings sheet and tell us if anything changed.”

Cora confirms what she set up: what she will do, when it runs next and how often. To change a schedule, ask her to cancel it and make a new one.

A schedule is one of two kinds:

Kind What you say What happens
One-off A date and a time It runs once, then shows as done.
Repeating Every so many minutes, hours, days or weeks, with a time of day and days of the week if you want them It keeps running until someone pauses or deletes it.

Any member of the mission can ask for a schedule. The schedule keeps the name of the member who asked, and Cora treats its instruction as that member’s request each time it runs.

Schedules work the same way in a hero’s own mission. A hero that another mission has called in can see its own mission’s schedules, but it cannot make, pause, resume or delete one: work that runs on its own later would outlast the call’s time limit and the caller’s caps. To have a hero do something every week, schedule it in your own mission instead: the scheduled run calls the hero in like any call, within the usual limits, and if you ask the hero itself for a repeat it says so (D0799).

Cora is told the current date and time at the start of every piece of work, in your organisation’s time zone. So she can answer “what is the date today?” and work out “next Tuesday” correctly.

A schedule uses your organisation’s time zone unless you name another one, such as “9 am Perth time”. A daily time stays at the same clock time when daylight saving starts or ends.

  • No more often than every 15 minutes. Ask for less and Cora says so and makes nothing.
  • Up to 5 minutes late. Cora checks for due schedules every 5 minutes, so a run starts at its time or up to 5 minutes after. If she is busy with other work in the mission, it waits its turn.
  • At most 10 active schedules in a mission. Paused and done schedules do not count. At the limit, pause or delete one first.
  • Missed runs are not made up. If Cora AI was down when runs were due, the schedule runs once when it is back and then carries on at its usual times.

A scheduled run is ordinary work:

  • Anything that changes something in a connected service still waits for a person’s approval card. While a card is waiting, the schedule’s run that is already due waits behind it, and runs that fall due meanwhile are skipped, not piled up: after the approval it runs once, then carries on at its usual times. The same holds for up to 2 hours while a run has been sent but has not started yet. After that the run counts as lost, for example after an outage or a dropped message, and the schedule carries on. If the lost run turns up later, it is skipped, so a schedule never runs twice for one time.
  • The work counts towards your organisation’s spend cap. At the cap, scheduled work stops like all of Cora’s work until the cap is raised or the month ends.
  • Cora posts the result in the mission, where every member can read it.

A repeating schedule that has run 5 times in a row with no message from a person in the mission pauses itself. The fifth run still happens, and Cora then posts that the schedule is paused and how to resume it. This stops a forgotten schedule from running, and spending, for ever.

Any message from a person in the mission starts the count again.

Who In mission details By asking Cora in the mission
Any member of the mission See the mission’s schedules. Make a schedule, list them, and pause any schedule.
The member who asked for a schedule See it. Also resume or cancel that schedule.
Mission admins Pause, resume or delete any schedule. Also resume or cancel any schedule.

Pausing is open to everyone in the mission because it is a safety stop: anyone can stop a schedule that is doing the wrong thing. Resuming and cancelling belong to the member who asked for the schedule and to the mission’s admins. If someone else asks Cora to resume or cancel it, she says she cannot and why.

Being an org admin does not by itself let you change a mission’s schedules. An org admin who is in a mission but is not one of its admins is treated like any other member.

To see a mission’s schedules, open Mission details and choose the Overview tab. The Schedules section lists each one: what Cora does, how often, when it runs next, who asked, and whether it is active, paused or done. Admins of the mission see Pause or Resume and Delete beside each one.

You can also ask Cora: “what schedules do we have?”, “pause the bookings check” or “cancel the Friday reminder”. Resuming or cancelling this way works when the member asking is the one who set the schedule up, or a mission admin.

A schedule also pauses when its mission is no longer active, and is removed if its mission is deleted.

  • It cannot be made from your private chat with Cora. Private chat turns are never stored, so a schedule asked for there would have nothing to run from. Ask in the mission instead.
  • It cannot react to an event, such as a new email or a changed file. It runs on time only.
  • It sends no email of its own. The result is a post in the mission; your usual notices apply.

Cora uses four built-in tools for schedules: create_schedule, list_schedules, set_schedule_state (pause and resume) and cancel_schedule. Only Cora herself has them; her helpers do not. A called-in hero has only list_schedules. They act only on the mission she is working in.