Skip to content
Yardmaster Guide

See everything that runs on its own

My Automations lists every scheduled job, recipe schedule, sweep, rule, drip, alarm and scheduled message in one place, so you can spot what is broken and pause anything.

Beginner2 minutes

My Automations shows everything Yardmaster runs for you without being asked, in one list: scheduled jobs, recipe schedules, sweeps, rules, drips, alarms and scheduled messages. Check it to see what is broken, what runs next, and what costs money.

Open the list#

  1. In the sidebar, open Automation, then My Automations.

  2. Pick a tab: Needs attention, Coming up or Everything.

  3. Click a row to open the panel where that automation lives.

  • Needs attention lists anything whose last run failed, that looks stuck, that missed a run, that waits for your approval, or a one-time automation whose date has passed.

  • Coming up lists what is due to run between now and the end of tomorrow, soonest first.

  • Everything lists every automation, grouped by kind, such as Scheduled jobs, Recipe schedules, Sweeps and Alarms.

Which automations cost money?#

A row marked Uses AI credits starts AI work each time it runs, which is billed to your Claude plan or an API key. The mark appears on scheduled jobs, recipe schedules, workflows, Slack posts and sweeps that start AI work.

A missing mark does not always mean free. Rules and Reviewer are never marked: a rule with an AI condition or a CLI Session action spends on every match, and Reviewer spends when it prepares a review. Check a rule's actions yourself in rules.

Pause, resume or run one now#

In the desktop app, open Automation > My Automations in the sidebar. Each row that allows it has Pause (or Resume) and Run now. Pause stops it running on its schedule until you resume it; it is the same switch as in the automation's own panel. For an automation marked Uses AI credits, Run now first asks Run this now? and nothing runs until you confirm.

Plain scheduled jobs also have a Delete button, which asks you to confirm first.

Did this help?