Running unattended routines and triggers
Approvals raised by a routine, trigger, or another bot expire after about ten minutes and the action never runs. Design every unattended job to end in a draft, a file, or a report, and move the permission step to when a person is there.
The line every routine prompt carries
This run is unattended. Never request an approval during it.
If you reach a step that needs one, stop there, write what you would
have done and why, and put it in the report under "waiting for
approval". Then continue with the steps that do not need one.
Creating a routine
- Schedule. Write it in plain words and confirm the time zone back before saving. Reads and prep run nightly, summaries weekly; hourly only when the source really changes hourly.
- Inputs. If an input is missing or a source is unreachable, report the failure. Never substitute older data as today's.
- Idempotent. Every step must be safe to run twice. Before any step that creates or sends something, check whether it already happened; if a step can't be made safe, stop before it and flag it.
- Output. Name the exact destination (file, issue, draft, report line). Stay quiet when nothing changed, but log the run so a silent run and a failed run can be told apart.
- Test run. Run it once against safe inputs and read the full output before trusting the schedule. Test runs do real work.
Creating a trigger
- Fire only when ALL are true: a specific source (one channel, repo, or label), a specific phrase or sender, and not already handled in the last N hours.
- One action when it fires, read-only or draft-only. Then stop; no chaining into other work.
- Before saving, estimate how many times it would have fired in the last 7 days. More than 10 means narrow the match.
Done checklist
Circuit breaker (bot-skills#39, Adam GO Nov 2, 2026)
After 3 consecutive failures from the same source, pause the routine and tell Charles in one line naming the routine and the error, so he can resume it. Kill rule: if no pause fires in 30 days, remove this block.
1---2name: running-unattended-routines-and-triggers3description: >-4 Use when creating or editing a scheduled routine or event trigger that runs5 while nobody is watching, so it never stalls on an approval, never fires on6 noise, and is tested before it is trusted.7metadata:8 source: https://skillmd.com/skills/bostonaholic/running-unattended-routines-and-triggers9---1011# Running unattended routines and triggers1213Approvals raised by a routine, trigger, or another bot expire after about ten minutes and the action never runs. Design every unattended job to end in a draft, a file, or a report, and move the permission step to when a person is there.1415## The line every routine prompt carries16```17This run is unattended. Never request an approval during it.18If you reach a step that needs one, stop there, write what you would19have done and why, and put it in the report under "waiting for20approval". Then continue with the steps that do not need one.21```2223## Creating a routine241. **Schedule.** Write it in plain words and confirm the time zone back before saving. Reads and prep run nightly, summaries weekly; hourly only when the source really changes hourly.252. **Inputs.** If an input is missing or a source is unreachable, report the failure. Never substitute older data as today's.263. **Idempotent.** Every step must be safe to run twice. Before any step that creates or sends something, check whether it already happened; if a step can't be made safe, stop before it and flag it.274. **Output.** Name the exact destination (file, issue, draft, report line). Stay quiet when nothing changed, but log the run so a silent run and a failed run can be told apart.285. **Test run.** Run it once against safe inputs and read the full output before trusting the schedule. Test runs do real work.2930## Creating a trigger311. Fire only when ALL are true: a specific source (one channel, repo, or label), a specific phrase or sender, and not already handled in the last N hours.322. One action when it fires, read-only or draft-only. Then stop; no chaining into other work.333. Before saving, estimate how many times it would have fired in the last 7 days. More than 10 means narrow the match.3435## Done checklist36- [ ] Unattended line is in the prompt37- [ ] Time zone confirmed38- [ ] Missing-input and failed-check paths report instead of guessing39- [ ] Every create/send step checks for a prior success first40- [ ] Test run output read and test-run note recorded (format in starting-a-routine-skill-first step 8)41- [ ] Trigger fire estimate is 10 or fewer per week4243## Circuit breaker (bot-skills#39, Adam GO Nov 2, 2026)44After 3 consecutive failures from the same source, pause the routine and tell Charles in one line naming the routine and the error, so he can resume it. Kill rule: if no pause fires in 30 days, remove this block.