Lesson 7 · 18 min
The schedule turns the pipeline into a channel: one run a day, at a set time, without you having to remember. But a schedule without a gate means posting the wrong thing faster. In this lesson, you’ll write the timer, decide what happens on a day with no topic, and run a week approving each video until you stop having to reject them.
Start the lesson
Goal: write your channel’s schedule and run a week with manual approval, turning each rejection into a rule.
Click each block. This is what happens every early morning in a radar.
Each radar runs at a different time (02:00, 05:00, 08:00) so they don’t compete for the GPU and avatar studio.
The finviral model, for you to adapt.
40 to 60 seconds on what the sources published yesterday and the day before.
Monday to Friday, 02:00 · "daily" run
90 seconds to 2 minutes with a recap of the week. The radars also produce a long 16:9 video, "The week explained," from 5 to 7 minutes.
Saturday, 02:00 · "weekly" run
About 90 seconds on what the sources expect for next week.
Sunday, 02:00 · "Sunday" run
Decide in advance what happens on a day with no news: no video, and the message "no story" with the reason. Forcing a video on a slow day is the first step toward publishing the wrong thing.
no story: none of the channels published a new video during this period.
A systemd timer for your user (finviral works this way). Replace <canal> and the script path.
[Unit] Description=<canal> — daily at 02:00 [Timer] OnCalendar=Mon..Fri *-*-* 02:00:00 Persistent=false [Install] WantedBy=timers.target
[Unit] Description=<canal> — daily run After=network-online.target [Service] Type=oneshot ExecStart=/bin/bash %h/projetos/<canal>/auto/rodar.sh diario TimeoutStartSec=10h MemoryMax=60G Nice=5
systemctl --user daemon-reload systemctl --user enable --now <canal>-diario.timer systemctl --user list-timers '<canal>-*' # skip one run without disabling the schedule echo "2026-10-17 diario" >> auto/pular.txt
# minute hour day month day-of-week command 0 2 * * 1-5 /bin/bash $HOME/projetos/<canal>/auto/rodar.sh diario
With Persistent=false, a missed run (the machine is off at 02:00) does not run late when the machine comes back on. For a daily radar, a video about yesterday published in the afternoon is no use.
TimeoutStartSec and MemoryMax are limits: a run that gets stuck is stopped, and one that uses too much memory won’t bring the machine down. A run with no limit that gets stuck at 02:00 is still stuck at 09:00.
Run it for a week. Interrupt it halfway through, then run it again.
Illustrative browser simulation. Wednesday with no topic is intentional, to show that an empty day is a normal result, not an error.
Exercises 5 and 6 in sequence 4.
Choose the frequency and write the schedule (systemd timer or cron), including what happens on a day with no topic and where the failure alert goes.
Done when: the schedule is written, list-timers (or crontab) shows the next run, and you know what happens on a day with no topic.
Run for a week with manual approval before each post. Note what you reject and why; each rejection becomes a rule in regras.md.
Done when: you’ve gone 3 days in a row without needing to reject anything. Only then consider removing the gate from a step.
Completed exercises: jornada-agentes/exercicios/04-redes.md.
The explanation appears after you answer.
Question 1 of 4
When is it reasonable to remove the gate from a step?competency
Question 2 of 4
It’s 9 a.m. and you haven’t received anything from the bot. What does that mean?
Question 3 of 4
Tomorrow is a holiday, and you don’t want a video. What can you do without turning off the schedule?
Question 4 of 4
Why use Persistent=false on a daily radar timer?
Choose an option. The explanation appears after your attempt.