Skip to content
FlintFlintby Torch
← LevelsBuilder · B12

Cron in plain English

Build-along · ~12 min at your own keyboard

Scheduled triggers are the 'while you sleep' half of automation: every weekday at 6am, every Friday at 4, first of the month. Modern platforms take the schedule in plain English. Rule stands: schedule the deterministic scripts, not the unattended LLM.

The long version: Scheduled jobs ↗

Mac: Mac: for a local fallback, run crontab -e and add a line like 0 7 * * 1 /path/to/script. The Mac must be awake.

Windows: Windows: for a local fallback, use Task Scheduler. Create a Basic Task, pick the trigger, and point the action at your script. The PC must be on.

Do this

0/4

Checkpoints

  • ▸You should now see your script deployed with a schedule showing in the platform.
  • ▸You should now see a first run in the log at the scheduled time.
  • ▸You should now see a second run at the next time, with no help from you.
The three ways this goes wrong
  • The job never fires. — Check the schedule time zone. Most platforms use UTC.
  • It fires but the output is empty. — Open the run log. The script may rely on a local file that is not in the deploy.
  • It fires twice or at the wrong hour. — Re-read the schedule line and confirm there is only one job.

Share what happened

Paste the schedule, evidence of two untouched automatic runs, and their outputs (trimmed).

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.