Scheduled and recurring work
A job can run on a schedule rather than waiting to be asked. You set one up by asking Sanaf or from the console. A schedule carries its own timezone, posts where it was set up, and a new one Sanaf proposes always needs your approval, with what it will cost a month on the card.
Last updated 2026-09-24.
What a schedule is
A schedule is a standing instruction: run this, this often, in this timezone. It is not a separate automation, which is why it inherits the job description, the connected apps and the approval rules you already set.
Ask for one the way you would ask a person, "every Monday at nine, tell me which accounts went quiet", and Sanaf proposes it. The approval card shows what will run, how often, and roughly what it will cost a month. Work that repeats exactly, Sanaf can turn into a small program that runs without thinking each time, and the card shows you that program before you approve it.
The timezone is stored with the schedule rather than taken from whoever created it. A daily report meant for a nine in the morning read stays at nine when the person who set it up is travelling.
Setting one up
- 1
Write the standing request
Say what you want done and what done looks like, in the same words you would use asking a person. "Every Monday, tell me which accounts went quiet last week and which one is worth a call" is a good one.
- 2
Pick the cadence and the timezone
Every few minutes or hours, daily, weekdays, weekly on chosen days, monthly, or once on a specific date. Set the timezone to the one the output is read in, not the one you happen to be in when you set it up.
- 3
Check what it may do unattended
Nobody is watching a scheduled run. If the job should send something at four in the morning, that kind of action has to be allowed without being limited to work somebody is watching.
- 4
Say where the result goes
It posts where it was set up: the channel, the thread, or the console chat you asked in. A scheduled job that produces something nobody sees is the most common way this goes wrong.
When a run fails
A failed run is recorded with what it was trying to do and where it stopped. When a schedule starts failing, Sanaf tells the person who set it up once, reminds them once a day while it lasts, and goes quiet the moment it works again. It does not silently retry forever, and it does not quietly stop existing.