Situations
I want Q to look at production errors on a schedule every day
Each situation has three parts: what to tell Q, what happens, and what you need to do. The wording is only an example; say it in your own words.
First-time setup
- Sessions need a way to see the errors: for example, the command-line tool of the error platform you use, installed and signed in on this computer, or logs they can read. Q itself doesn't run commands; looking is left to sessions.
What to tell Q
What to say"Every weekday at nine, look at yesterday's production errors. If there are new ones, create tasks; if not, just say 'no new errors'."
What happens
- Q drafts a scheduled task, and it only takes effect once you click "Start" in "Needs you".
- Every time it's due, a round starts in the "Scheduled: look at production errors" topic, so you can look back at what was done each day.
- If a task created by the last run isn't done yet, this run is skipped.
- If the computer was asleep and missed it, it makes up one run if it wakes within 12 hours.
What you need to do
- The first time, click "Run now" to try it and see whether the result is right.
- After that, check the results in the morning brief or in that topic, and accept any new tasks as usual.
Tipeach run is an extra round for Q, using your own account; when less than 10% of quota is left, that run is skipped.