Frequent schedules repeat useful actions and mistakes
A task that runs every fifteen minutes runs up to 96 times in a day. That can multiply model use, notifications, file changes, and mistakes. Begin on demand. Try a daily schedule after several successful manual runs. Increase the frequency only after the results remain consistent.
Require approval for actions with outside consequences
- Have the Bot prepare a draft and ask a person to approve publication.
- Have the Bot propose recipients and ask a person to approve sending.
- Have the Bot report possible deletions and ask a person to approve them.
- Have the Bot create a change plan and ask a person to approve production changes.
- Have the Bot identify financial or legal questions and send them to a qualified person.
SourcesOfficial cron guide
Record what happened during each run
A useful routine records what it read, what it produced, what it changed, and which decision it left for a person. This record makes the result easier to review and compare with later runs.
