A reminder in DataMind Oda brings a message back to you later in the same conversation, once or on a fixed interval. This page lists what Oda accepts when it sets one, how a due reminder arrives, and the limits around it. For the everyday walkthrough, see Reminders.
A reminder is set with a prompt and exactly one time rule:
prompt must be non-empty after trimming.after_seconds: a delay, a positive whole number of seconds, as in "remind me in 30 minutes";at: an exact time, either an instant with an explicit offset, such as 2026-09-01T15:00:00+08:00, or a local date and time with one named zone, such as 2026-09-01, 15:00:00 and Europe/;every_seconds: a repeat, a whole number of seconds, at least 300 (five minutes).A request that gives more than one form, or none, is refused: schedule_create accepts exactly one of after_seconds, at, or every_seconds.
Reminders belong to the conversation they were set in, and Oda delivers them only there. Only the main conversation can set one; the helper agents Oda runs on the side cannot.
UTC, or a standard name in Area/ form, such as Europe/. A zone Oda cannot read is refused: time_zone must be UTC or a valid IANA Area/The scheduled time must be strictly in the future.The scheduled time must be representable as a four-digit-year RFC 3339 UTC instant.The local at time does not exist in the selected time zone. When the clocks go back and the same local time happens twice, Oda takes the earlier instant.[SCHEDULE REMINDER] or [SCHEDULE REMINDER BATCH] when several repeats arrive together, and carries a standing instruction to present it to you as a reminder, not as new instructions.A reminder is content for you. Oda presents it as a reminder when it arrives and never treats it as a new instruction; new work still starts only when you ask for it.
schedule-1, schedule-2 and so on. Oda returns the id when it sets a reminder, and the same id is what a delete uses.schedule_not_found.| What happened | What Oda reports |
|---|---|
| An empty prompt | prompt must be non-empty after trimming. (invalid_prompt) |
| More than one time rule, or none | schedule_create accepts exactly one of after_seconds, at, or every_seconds. (invalid_selector) |
| A delay that is not a positive whole number of seconds | after_seconds must be a positive safe integer. |
| A repeat below five minutes | every_seconds must be at least 300. (frequency_too_high) |
A zone that is not UTC or a standard zone name | time_zone must be UTC or a valid IANA Area/ (invalid_time_zone) |
| A time already in the past | The scheduled time must be strictly in the future. (not_future) |
| A local time in a daylight-saving gap | The local at time does not exist in the selected time zone. (invalid_rule) |
| A time outside the representable range | The scheduled time must be representable as a four-digit-year RFC 3339 UTC instant. (time_out_of_range) |
| A delete without a usable id | schedule_delete id must be non-empty without surrounding whitespace. |
A whole operation can also fail:
The session schedule log is corrupt. (corrupt_schedule_log): the conversation's reminders cannot be read.Schedule persistence is uncertain; retry with schedule_list before relying on this result. (persistence_uncertain): a change could not be confirmed as saved, so Oda lists the reminders instead of claiming success.The schedule operation failed. (internal_error): the operation failed.A reminder comes back to the conversation you set it in. A scheduled task is a different feature: it runs on its own, in a new conversation, at the time you choose. For work that should run by itself, see Schedule recurring tasks.
No. A reminder has exactly one time rule: a delay, an exact time, or a repeat. A request that mixes the forms is refused: schedule_create accepts exactly one of after_seconds, at, or every_seconds. To keep coming back, set a repeat; it runs on the interval you set, counted from when you set it.
Give the date and the time, and name a zone when it is not your computer's. Oda accepts the time as an instant with an offset, such as 2026-09-01T15:00:00+08:00, or as a local date, a local time and one named zone, such as Europe/ or UTC. A zone it cannot read is refused: time_zone must be UTC or a valid IANA Area/
No. A reminder comes back to the conversation you set it in, and only while that conversation is live. A scheduled task runs on its own in a new conversation, at the time you choose. See Schedule recurring tasks.
Ids look like schedule-1, and Oda returns one when it sets a reminder; the list shows each reminder's id beside it. Give the exact id when you ask Oda to delete a reminder.
Missed intervals are not replayed one by one. A repeat that could not run while the conversation was closed comes back once, for its latest due time, and then keeps its interval.
No. It shows what is still waiting, as scheduled or overdue, so it is not a delivery receipt. A reminder that fired was queued and recorded in the conversation; whether Oda's answer succeeded or you read it is not recorded there.
No. There is no edit; ask Oda to delete the reminder by its id and set a new one instead.
No. Reminders belong to the main conversation: Oda sets and manages them there, and the helper agents it runs on the side cannot set one.