Loading the documentation…
In DataMind Oda, a reminder brings a message back to you later in the same chat. Ask for one in your own words, one-time or repeating, and Oda keeps it with the chat. This page covers asking for a reminder, how it arrives, and what happens when the chat closes or is archived.
Ask as you would ask for anything else in Chat with Oda:
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. Only the main chat can set a reminder; the helper agents Oda runs on the side cannot.
When Oda sets the reminder, it tells you when the reminder will come back. The step that creates one leaves a record row titled Create reminder in this conversation; listing and deleting leave their own rows, List reminders in this conversation and Delete reminder in this conversation. How to read such rows is covered in Goal, schedule and job records in chat.
Europe/ or UTC; a zone that Oda does not recognise is refused: time_zone must be UTC or a valid IANA Area/The local at time does not exist in the selected time zone. Pick a time just before or after the change. When a change makes the same time happen twice, Oda uses the earlier one.schedule-1. Oda returns the id when it sets a reminder, and a delete uses the exact id.schedule_not_found.| What happened | What Oda reports |
|---|---|
| An empty prompt | prompt must be non-empty after trimming. |
| More than one time rule, or none | schedule_create accepts exactly one of after_seconds, at, or every_seconds. |
| 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. |
A zone that is not UTC or a standard zone name | time_zone must be UTC or a valid IANA Area/ |
| A time already in the past | The scheduled time must be strictly in the future. |
| A local time in a daylight-saving gap | The local at time does not exist in the selected time zone. |
| A time outside the representable range | The scheduled time must be representable as a four-digit-year RFC 3339 UTC instant. |
| 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.: the chat's reminders cannot be read.Schedule persistence is uncertain; retry with schedule_list before relying on this result.: a change could not be confirmed as saved, so Oda lists the reminders instead of claiming success.The schedule operation failed.: the operation failed.A reminder comes back to the chat you set it in. A scheduled task is a different feature: it runs on its own, in a new chat, at the time you choose. See Schedule recurring tasks.
The reminder waits. It is delivered only while the chat is open and Oda is free, so a closed chat keeps it as overdue until you open the chat again.
No. A reminder arrives only as a message in the chat itself; Oda sends no email, text message or notification for it.
At the shortest, every five minutes. A repeat runs on the interval you set, counted from the time you set it, and it keeps that rhythm even if an occurrence is missed.
Not as a calendar rule. A repeat runs on an interval, counted from the time you set it, so it cannot follow chosen weekdays. For work that should run on its own every weekday morning, use a scheduled task: Schedule recurring tasks.
Ask Oda to list the reminders in the chat, or to delete the one you mean. Deleting a reminder that has already finished changes nothing; Oda reports that it found no reminder to delete.
A chat with reminders still waiting cannot be archived until they are stopped. Once stopped, the reminders are deleted, and they do not come back when you unarchive the chat.
No. A branch or a copy starts without the reminders of the original chat; each reminder belongs to the chat it was set in. What happens when you change a chat's past is covered in Conversation branches.
A reminder can only be set for a time still ahead of you. When the time has passed, Oda refuses it and reports The scheduled time must be strictly in the future. Ask again with a later time.
No. The reminder comes back as content for you to read: Oda presents it as a reminder and does not treat it as a new instruction. New work starts when you ask for it.
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.
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 chat: Oda sets and manages them there, and the helper agents it runs on the side cannot set one.