Routines tool
The canonical version always lives at https://tavina.ai/docs/friendly/tools/routines
Routines tool
The toolbar label for Tavina’s clock features is Clock Routines. It covers alarms, timers, recurring schedules, follow-up watches, protected system schedules, and history for recent routine activity.
Use Routines when something should happen later, repeat on a schedule, or be watched until a condition is met.
What you see in the PWA
Open Routines from the toolbar. The panel can show:
- Timers β countdown-style reminders.
- Alarms β reminders for a specific time.
- Recurring routines β scheduled jobs that repeat.
- Long-run jobs β lengthy background jobs with a long-run badge, live progress, and a cancel control.
- Watching β follow-up promises and conditional watches Tavina created from chat.
- System schedules β protected read-only jobs that subscribers can inspect but not edit.
- History β successful and failed routine events, including whether Tavina was notified.
The source UI uses status badges such as successful routine, failed routine, read-only system, agent notified, and delivered late for late catch-up deliveries (tavina/tavina#2876).
Alarms and timers
Use an alarm when the reminder belongs to a clock time: Remind me at 4 PM to call the vet.
Use a timer when the reminder belongs to a duration: Set a timer for 25 minutes.
Examples:
- “Set a timer for 15 minutes called check the oven.”
- “Set an alarm for 7:30 tomorrow morning.”
- “Change the laundry timer to 40 minutes.”
- “Pause my morning routine while I am on vacation, then resume it when I am back.”
- “Cancel the laundry timer.”
- “What alarms are active?”
Alarms and timers can be changed in place: ask Tavina to rename a routine, move its
time, change a timer’s length, pause it, or resume it. Changing a routine keeps its
history instead of deleting and recreating it.
You can set everything in one request when you create an alarm or timer. That includes its tags and any instructions for what Tavina should do when it rings, for example: “Set a 20-minute timer tagged kitchen, and when it goes off, remind me to check the bread and the oven temperature.” You never need to create it first and edit it afterward.
If you want to check the setup before Tavina saves it, ask for a preview. Tavina shows exactly what it would create or change and saves nothing until you confirm.
When you ask for an alarm or reminder in chat, that request is the approval: a one-off alarm, timer, or reminder you asked for is saved right away, with no extra confirmation step β and the same goes for an edit Tavina can clearly match to what you just asked for, such as rescheduling it to a time you named. Tavina still checks with you first for changes it cannot tie to your request β recurring or bulk changes, or edits that came up on their own β so a surprise never lands in your Routines silently (tavina/tavina#2645).
When an alarm rings
When an alarm rings, its modal offers two actions: SNOOZE and DISMISS.
- SNOOZE quiets the alarm and re-arms it to ring again within 15 minutes. The routine stays listed in Routines with its updated next-fire time, so you can see when it will ring again.
- DISMISS stops the alarm without re-arming it.
Time zones, travel, and daylight saving
Recurring routines track your current time zone. If you travel or change your Routines time zone, a daily 6:00 AM reminder stays a 6:00 AM reminder β its firing time is recomputed for the new zone so the wall-clock time never moves. One-off alarms and timers pinned to a specific moment are instant-locked instead: they fire at that exact moment regardless of where you are. Across daylight-saving changes, recurring routines keep the intended clock time, so a 6:00 AM routine fires at 6:00 AM on both sides of the switch. When Tavina mentions routine times in chat or your morning briefing, it reads the routine’s local display time, never a raw stored timestamp (tavina/tavina#2751).
Recurring routines
Use recurring routines for schedules that repeat, such as a daily review or a weekly planning reminder.
Examples:
- “Every weekday at 8 AM, remind me to check today’s priorities.”
- “Every Sunday evening, ask me to plan meals for the week.”
- “Pause the weekday planning routine.”
Recurring routines support more than daily and weekly patterns:
- Monthly β a chosen day of the month (
the 15th of every month), the nth weekday of a month (the first Monday of every month), or the last day of the month (the last day of every month). - Yearly β an anniversary-style date (
every August 11). Yearly reminders for February 29 fire on February 28 in non-leap years. - Intervals β every N days or weeks (
every 10 days,every 2 weeks).
A repeating routine can also have an end condition: stop after a chosen date (until the end of March) or after a set number of occurrences (five times, then stop). Repeat times hold the same local clock time across daylight-saving changes, so a 9 AM routine keeps firing at 9 AM local time.
If you want to double-check a schedule before committing to it, ask Tavina to describe it: it will explain the schedule in plain words and show the next several fire times.
If a routine fires late
Sometimes a routine cannot start on time β for example after maintenance or an update. By default, Tavina catches up: the routine runs as soon as it can, just a little late. Catch-up now has a safety bound (tavina/tavina#2876): a one-shot routine that is more than four hours late is never delivered as if nothing happened β the occurrence is consumed with a visible skipped history row carrying the reason (catch-up lateness bound), so a stalled scheduler cannot dump a multi-day backlog of stale alarms. Recurring routines are exempt (the next occurrence heals the schedule), a per-routine lateness bound you set explicitly still wins over the default, and when a backlog is recovered inside your quiet hours its delivery is held until the quiet window ends β unless the routine is tagged time-sensitive or urgent, or is invisible.
For time-sensitive routines, catching up can be wrong β a 6 AM alarm that fires at 6:40 is noise, not help. Any routine can instead be set to skip when it’s too late. You choose how late is too late (15 minutes by default). A skipped occurrence is never thrown away silently: it appears in the routine’s history as Skipped (Too Late) with the reason, so you can see exactly what didn’t run and why. Ask Tavina to set this when creating a routine, or change it later β for example, “If the morning briefing is more than ten minutes late, skip it.”
A routine that is delivered late β within the allowed window, but after its deferral window β is marked honestly too: its history entry carries a Delivered Late badge with the detail, so a late delivery never reads as an on-time success (tavina/tavina#2876).
When a routine run fails
If a routine run fails β an error, a timeout, or the run hitting its tool limit β Tavina sends you one short notice with the routine’s name, what went wrong in plain words, and a link to the routine. The notice is quiet by design: while a routine keeps failing, you get at most one notice per failure streak rather than a new alert for every failed run. A successful run resets the streak, so the next failure notices you again.
If you’d rather not get these notices for a particular routine, ask Tavina to turn them off for it. Failures always show in the routine’s history either way.
Organizing routines with tags
Routines can carry tags β short labels you choose, like focus, workout, or bills β so related routines can be managed together. Ask Tavina to tag routines when creating or editing them, to list routines sharing a tag, or to enable, disable, or delete every routine with a tag in one step. Bulk actions by tag carry the same safety checks as bulk actions by list: Tavina confirms exactly how many routines will change before doing anything, stops if the number does not match what you said, and keeps deleted routines recoverable.
Before a bulk action, you can ask Tavina which routines a tag currently matches. Tavina lists them and gives the count without changing anything, so you know exactly what a bulk action would touch. If a tag matches no routines, Tavina says so plainly, and when you expected zero matches, nothing happens and nothing is changed.
Running one routine after another
A routine can be set to start only after another routine finishes successfully β for example, a cleanup reminder that waits until a scheduled report has completed. If the first routine fails, the waiting routine does not fire and is marked as skipped instead of silently re-running later. You can also make a routine run after another finishes regardless of outcome. Ask Tavina to inspect a routine’s dependencies to see what it waits on and what waits on it.
Long-run background tasks
Some jobs are too big for a normal chat turn β a deep overnight research pass or a large batch job. For those, Tavina supports long-run background tasks on Clock Routines jobs. Long-run is opt-in: it is set on the job when the job is created, never silently.
- A long-run job runs detached in the background. It keeps going even if you close the app or disconnect, and it is not bound to the short responsive window of a normal chat turn.
- Each job gets a time budget: four hours by default, eight hours at most. When the budget runs out, the job stops.
- Long jobs work in legs. The job pauses at checkpoints and continues on its own, so a hiccup does not lose the work already done.
- The Clock Routines panel shows each long-run job with a long-run badge and live progress: its heartbeat, deadline, legs completed, and token use.
- You can cancel a long-run job from the panel. A cancel takes a moment to reach the job; the panel shows a pending-cancel notice until it takes effect.
- You are notified when the job completes or fails, using the same device-notification path as other routine alerts (see Mobile and background alerts).
- A long-run job uses Tavina tokens and budget as it works, and that use counts against your daily quota, just like normal usage.
Long-run mode is new and currently available on the dev channel.
Mobile and background alerts
When an alarm, timer, or completed routine fires, Tavina can send a real device notification to each phone or computer where notifications have been fully enabled on that device β including when the app is closed and the screen is locked.
For reliable mobile alerts:
- Install Tavina on the device you want alerted. On iPhone or iPad, use Safari’s Add to Home Screen flow on iOS 16.4 or newer β a Safari tab cannot receive iOS push alerts.
- Sign in, open Settings β Notifications, and tap Enable notifications on this device. Wait for the Ready status: permission alone is not enrollment, and each device is enrolled separately. See Turning On Notifications.
- Run the built-in delayed self-test with the phone locked to confirm the whole path works on that device.
What you can honestly expect:
- A desktop window being open does not stop your phone from being alerted. Each enrolled device is delivered to on its own.
- Your phone’s silent mode, Focus/Do Not Disturb, sound, vibration, and lock-screen preview settings are always honored. Tavina does not force sound, vibration, custom locked-screen sounds, or continuous ringing, and it cannot make an alarm arrive at an exact instant.
- Tapping a routine notification opens that routine directly. A late or replayed alarm notification is marked as possibly already ended instead of ringing as if it were current.
- Silent mutes the chime only: the in-app popup and the device push still arrive, and the fire is still recorded in history. To suppress the popup and the push, the routine must be Invisible (tavina/tavina#2879).
Dismissal across devices
When you dismiss, snooze, delete, or disable a ringing routine on one device, Tavina sends a follow-up signal so the matching notification closes on your other devices where closing is possible. Phone operating systems do not let a web app silently clear every notification on another device in every case: if a notification cannot be closed remotely, it simply stays until you clear it β it will not ring again or double-alert. Each recurrence of a recurring alarm gets its own fresh notification.
notify_agent behavior
Some routines can notify Tavina when they fire. The Routines history can show an Agent notified badge for those events.
Use this when you want Tavina to react, not merely display a reminder. For example:
- “At 9 AM, remind me and ask me what my top priority is.”
- “When the timer ends, have Tavina prompt me for the next step.”
For ordinary reminders, a notification without agent follow-up is usually enough.
If notifying Tavina times out, the dispatch is retried once automatically, so a single slow moment doesnβt fail the notification. If a firing still fails, its History entry shows the real error detail rather than a generic timeout message, which makes it much easier to see what actually went wrong.
Delivery flags: Silent, Invisible, and Notify Tavina
Every routine has three delivery flags, and their meanings are exact (tavina/tavina#2879). The tooltips in the routine editor say the same thing Tavina’s own tool documentation says β one canonical contract, two surfaces:
- Silent mutes the chime only. The in-app popup and the device push still arrive, and the fire is still recorded in history. Use it to keep the notice but lose the sound.
- Invisible suppresses the trigger-time notices: no in-app popup and no device push. The fire is still recorded in history. Invisible forces Silent on β there is no popup to chime in β and Tavina tells you when it makes that change.
- Notify Tavina wakes Tavina at fire time. Tavina acts on the routine’s instruction and writes its own reply; that reply is a separate surface and is never suppressed by Silent or Invisible.
Auditability is not a flag: every fire lands in Routines history with its flags recorded, whatever combination is set.
| Flags | Chime | In-app popup | Device push | History | Tavina wakes |
|---|---|---|---|---|---|
| (none) | yes | yes | yes | yes | no |
| Silent | no | yes | yes | yes | no |
| Invisible (Silent forced on) | no | no | no | yes | no |
| Notify Tavina | yes | yes | yes | yes | yes |
| Silent + Notify Tavina | no | yes | yes | yes | yes |
| Invisible + Notify Tavina | no | no | no | yes | yes |
Two combinations get special handling:
- Silent + Invisible without Notify Tavina means nobody is notified β only history records the fire. It is allowed, with a clear warning at save time. Its real use is structural: a Clock dependency anchor that other routines can wait on (“start after that event”). For scheduled background agent work, add Notify Tavina; for Automations-style scheduling, use the automation’s schedule time instead of a no-notification routine.
- Invisible without Silent is contradictory β there is nothing to chime in β so saving sets Silent to match and tells you so.
To mute the chime without touching anything else, pick No chime (muted) as the routine’s sound. That is a first-class setting, and it fixes a trap: leaving the sound field empty does not mute anything β an empty sound resolves to your default chime. Choose “none” (or set Silent) to mute (tavina/tavina#2879).
Watching and conditional follow-ups
Watching is for promises like “check later whether this happened” or “follow up if I do not respond.” Watches may use Tavina’s judgment when the condition cannot be reduced to a simple clock time.
Examples:
- “If I have not replied to this by tomorrow afternoon, remind me.”
- “Watch for whether I confirm the appointment, then follow up if I don’t.”
See Watching and follow-up promises for the detailed explanation.
System schedules
Some schedules are protected system jobs. The Routines panel can show them as read-only or locked. That means they are part of Tavina’s operating schedule and are not normal subscriber-editable routines.
Do not try to edit protected system schedules from the subscriber panel. If something looks wrong, ask Tavina or support to explain it.
Routines or automations?
If the whole job is a reminder at a time β “every weekday at 8” β a routine is the right tool. If Tavina should instead run a multi-step workflow on a schedule or trigger, with conditions, approvals, and a run log, that is an Automation. And if something just needs to be checked until it happens, that is a watch.
One clock difference worth knowing: recurring routines re-anchor to your current time zone as you travel (see above), while an automation’s schedule is pinned to a single chosen time zone. Watches are different again β they do not fire at a clock time; they re-check a condition on a periodic interval until it becomes true.
Good habits
- Use clear labels so future you knows why a routine exists.
- Use alarms for times and timers for durations.
- Use recurrence only when a reminder truly repeats.
- Use notify-agent behavior only when Tavina should take a follow-up action.
- Use long-run mode for jobs that genuinely need hours, and remember its token use counts against your daily quota.
- Review history when you are unsure whether a routine fired.
- Use Invisible β not Silent β for fully background work; Silent only mutes the chime.