Run a cron job on a schedule
A cron job runs a command, a recipe or an agent session at the times you choose, such as every weekday at 9am, as long as Yardmaster is open.
A cron job does a task for you on a schedule: run a script every night, start an agent every weekday morning, or run a recipe once a week. It runs while Yardmaster is open, even if you are not looking.
Make a cron job#
In the sidebar, open Automation, then Cron Jobs.
Click + Add Job.
Give it a Name.
Under Job Type, pick Script (a command on your computer), Recipe, or Session (an agent with your Prompt, in a Project you pick).
Under Schedule, pick a preset such as Weekdays at 9am, or Custom... to type your own.
Choose Recurring, Run once or Run N times.
Click Create Job.
A job you create yourself starts on its schedule right away. Turn on Require Approval if you want to approve each run in your Inbox first. A job an agent creates for you always waits for your approval, and so does an agent's change to an approved job.
Run, pause or delete a job#
Click a job to see its settings and Run History. Run Now runs it once straight away. Disable stops it running on its schedule until you click Enable. Delete removes the job and its history after you confirm.
If you have used Yardmaster for a while, some jobs may have come from a recipe's schedule. For those, also pause that schedule under Recipe schedules in My Automations: disabling or deleting the job alone lets the recipe's schedule run again, and it spends like before.
What if Yardmaster was closed?#
A job only runs while Yardmaster is open. If your computer was off or asleep at the scheduled time, that run is skipped. Turn on Run if missed on a recurring job to have it run once the next time you open Yardmaster, for misses in the last 7 days. However many runs were missed, it catches up with one run, then carries on as normal.
Let an agent fix a failing job#
With Self-Healing on, when a job fails for good (after its retries), Yardmaster pauses it and starts an agent session in the job's project to fix it. The agent resumes the job once the fix works.
Failure alerts. When a job fails, Cron failure alerts puts a card in your Inbox (on at first).
Agents can schedule jobs too. Ask an agent "run this every day at 9am" and it can create the job; you approve it in the Inbox before it ever runs.
Keep the sidebar quiet. Visibility decides whether a recipe job's sessions show in the sidebar (Force silent, Force visible, or the recipe's own default).
Custom schedules use the standard five-part cron format, for example
0 9 * * 1-5for weekdays at 9am. The editor shows what your schedule means before you save.Turning it off stops it. Turning off Enable Cron Jobs in Settings hides the Cron Jobs row and stops your jobs from running on their schedule. A run that has already started finishes, but no retry or follow-on job starts. Turn it back on and each job runs again at its next scheduled time; runs missed while it was off are skipped, except a one-time job, which runs once when you turn it back on. Scheduled Slack posts are not affected.
Run now still works while it is off. Clicking Run now (for example in My Automations) runs the job once, but while the switch is off its retries and follow-on jobs are skipped.
Learn Yardmaster, Let it run itself: lesson 2 of 3
Put work on a schedule
Related
- Set an alarm or reminderType a reminder in plain words, like "every weekday at 7:30 AM stand-up", and Yardmaster rings at that time with Snooze and Dismiss.
- See your Google Calendar in YardmasterConnect Google Calendar to see your day, add and change events, get meeting reminders and ask an AI about your schedule.
- Let auto-replies answer your agentsAuto-replies answer or tidy up a session when its agent says something you expect, so work keeps moving while you are away.