Where and when automations run
Each kind of trigger has one place that runs it, so an automation runs once, even when you have several devices.
Who runs what
| Trigger | Runs where | Why |
|---|---|---|
| An entry is created, a value changes | Where the change was made, at once: on a device, or in the cloud on Pro. This holds for your taps, the AI and kzx. |
It feels instant and works offline. |
| A schedule, a date arrives, everything is done, data comes in | Pro: in Cloud Sync, after it has merged the changes of every device. Free: your one device, while it is on (Free has no automations in the cloud). | These depend on time or on the merged state, and only one place sees that. |
| A button or command | Where you pressed it. |
On Pro, these automations run in the cloud, as part of Cloud Sync. They run while every device is off. Free has Cloud Sync for one device, but no automations in the cloud. So on Free, these automations run on your one device, while it is on. With Cloud Sync off (desktop app only), they run on the desktop while it is on.
Some collections are end-to-end encrypted: only your devices hold the key. If you did not give Cloud Sync a key for such a collection, an automation that reads it runs on one of your devices instead. Cloud Sync picks one device, so only one runs it.
Instant for you
Example: you tick “Meditate” in Habits. The automation adds the tag Finished and adds 1 to Streak.
- A change to the same entry you tapped shows in the same moment as the tap.
- Changes to other entries follow a few milliseconds later.
- Scripts run right after the screen updates.
- AI and website steps run in the background and end with a toast.
One Undo takes back the tap and everything the automation did because of it.
Two devices that were offline
Your laptop and your phone are both offline. You tick the same habit on both.
- Double runs merge. An entry an automation creates gets an id made from the run’s trigger. If both devices ran the automation for the same tick, the two new entries are the same entry and become one.
- Adding numbers adds up. “Add 1 to Streak” is saved as “add 1”, not as the new total. Two offline +1s become +2.
- A device that gets a change through sync never runs it again.
- A tick that loses the merge: if another device later unticks the box, the run’s changes stay. The run history and “What changed” say “the tick that started this was undone on another device”, with Undo on the run. The app never guesses and reverts on its own.
Missed runs
Cloud Sync, or your Free device, was not running at 7:00. When it is back, it catches up missed runs from the last 14 days.
- Runs with no outside effects catch up by themselves.
- Runs that would ask the AI, call a website or send a message ask you first: “3 missed runs of Morning weather · Run the latest · Run all · Skip”.
Today, in the desktop app, an automation that makes or changes entries catches up each missed day once, by itself. One that runs an agent runs once, for the newest missed time, as in today’s app; the “ask you first” card comes with Cloud Sync. See See, switch on and run automations.
No runaway automations
- Loop stopper: one automation’s change can start a second, and that one a third, but no more. An automation’s own changes never start itself again.
- Volume guard: an automation that suddenly runs far more than usual (for example 100 runs in a minute) pauses and asks you.
- Big batches ask first: an import or a bulk edit that would start an automation more than 50 times asks once: “Run Weekly tag for these 2,000 new entries?”. An approved batch runs in the background in parts.
- Safe retries: if Cloud Sync retries a run, a key made from the automation, the change and the step stops anything happening twice.
Shared spaces
Automations of a shared space run only in the cloud, in the space’s own part of Cloud Sync, never on a member’s device. They read and write only the space’s collections and run on the owner’s allowance: the owner pays. The owner switches them on. Each member opts in before an automation may change entries that member made. Your own automations run as you and never inside a space’s part of Cloud Sync.