Schedules

#What a schedule is

A schedule is a job you say once and Rekhu Builder does on its own: every Monday morning, every night, on the first of the month, or once at a moment. Each run works in a thread of its own and ends with a report that goes to you.

Good jobs for a schedule:

Every Monday at 08:00 check the site for broken links and mail me the list.

On the first of every month, report which pages lost clicks in Search Console.

Every night at 02:00 make a backup of the database.

#Set up a schedule

Schedules are made in the chat, not on a form.

1. Set up where reports go. Under Preferences → Notifications, switch on e-mail, Slack or Discord and fill in the address or webhook, and press Save channels. Send a test message shows it works.
2. Say the job in the chat of the project, with how often and when.
3. Read the proposal. Rekhu writes the job out in full: its name, the instruction as it will run, how often and at what time with the time zone, the channels for the report, and whether it may change the live site.
4. Confirm. Press schedule it, or change something and say what. The schedule exists only after you agree.

A vague wish such as "check the site regularly" becomes a concrete proposal: what exactly, how often and when.

Setting up a schedule installs nothing and changes nothing on the site. The job chooses its tools when it runs.

#How often

Your account may limit how many schedules are active at once and how often one may run. When a limit is reached, the chat says so.

#What a scheduled run may do

Nobody is watching a scheduled run, so it follows stricter rules than a chat:

• It does the job fully and asks no questions. When a decision is needed, it names it in the report instead of deciding.
• It changes nothing live unless the schedule may. Without that permission it works on drafts and reports only; a change to a published page, a plugin, a setting or a user is written down as a proposal.
• It never publishes, deletes or installs a plugin unless the instruction names it and the schedule may change the live site.
• It stops at its cost cap. What was done so far stands, and the report says so.

A schedule may change the live site only when you said so while setting it up. The Schedules tab marks such a schedule with may change the live site.

#Watch and manage schedules

The project's Schedules tab lists every schedule with its rhythm, its state, how often it ran, the last run and where it reports. For each schedule you can:

• Run now: run it at once, without moving the next moment.
• Stop: end the run going on right now.
• Pause and resume it.
• Remove it.

Open a schedule to read its thread, read-only. Continue in the chat takes the last report into the chat, to ask about it or act on it.

#When a schedule keeps failing

A schedule that fails three times in a row is paused, and you are told once. A broken job does not keep spending credit every hour. Fix the cause, then resume it.

#Where reports go

Reports go to the channels the schedule names, among the ones that are on under Preferences → Notifications:

• E-mail to the address you set;
• Slack and Discord through a webhook.

A channel that is not set up is skipped, and the report says so. The bell at the top of the account shows what waits for you as well.

#Who pays

A scheduled run is paid from the credit like any other work. A schedule a client made is paid the way their own work is paid: from your credit within their budget, or from their wallet. See Clients.

#Next

• Changes to live pages: what happens when a schedule may change the live site.
• Credit and usage: what your schedules cost per month.