Schedule workflows

A Schedule workflow is the one thing in Dustav that the clock runs. Every morning, at an hour you set, Dustav checks each scheduled rule's condition against your real tables and your calendar, and drafts the due emails from the template you named — its exact words, its attached documents — into Drafts, for you to send.

It's the shape for "the day before", "the week after", "every Monday."

The sentence

"Every morning at 7, anyone whose class is tomorrow and who's bringing their own wheel gets the reminder, with the setup checklist attached."

Four parts:

• When — the morning hour. One run per morning serves every scheduled rule, at the earliest hour any of them names.
• The condition — who's due today. It's checked against your real data: a table ("class date is tomorrow", "rental is yes") and your calendar.
• The template — the words, by title. A schedule always drafts from a template; the run reads it fresh each morning, so an edit to the template lands the next day.
• The recipients — where the addresses come from. Three real sources: a column in a table the condition reads ("the Email column of that class's rows"), a fixed address you give when you set it up ("the landlord"), or you ("me", for a note to yourself). The run never invents or recalls an address. If the rule names none of the three, the item skips and says so.

Dustav settles all four in the conversation. If the class list is a table you already have, the condition writes itself. If there's no table at all ("on the 1st of every month, draft the rent transfer note to the landlord"), the condition is just the date and the recipient is just the address, and that's a complete schedule.

One email, or one each

By default a due class gets one email with everyone in Bcc — one draft to send, nobody sees the others' addresses. Ask for one email per person instead when the message should feel individual.

Never twice

Every draft the run prepares is written down in the rule's own ledger — which thing it was for, which morning. The next morning, the same class is already in the ledger and gets nothing. You can't get two reminders for one class by leaving the rule on, and you can't get a stale one by turning it on late: it drafts for what's due today, not for what it missed.

A run is capped so a bad condition can't flood Drafts; if it hits the cap it says so by name. And if your balance is out, the run parks and picks up the next morning it can.

What you see

When a morning run has drafts ready, it tells you — a notification with the count, opening onto Drafts. Each draft wears the template's subject and words, the documents the template carries as attachments, and a small marker saying which rule prepared it. You read, adjust if you like, and send. Same fence as everything else: prepared, never sent.

On the tab

A Schedule card leads with the time and the real next run ("Every morning at 7:00 · next run Tue"), then the condition and the recipients rule, then what it drafts from. Open it and the detail is three cards: the rule in full, the template it drafts from (a chip that opens the words in Templates, plus the documents that come with it), and the history — every morning it ran, what it drafted, each opening in Drafts.

Active pauses it. Ping me on a schedule controls only the "drafts are ready" note; the drafts land either way.

Not a schedule

A morning run checks conditions; it doesn't send at an arbitrary future time. To hold an individual email until a moment you pick, use Schedule send on the composer's arrow, which works on any draft. And an email that should go when a situation shows up — a customer wrote in, a supplier said done — is an Email workflow, not a schedule.