Recurring jobs

Work that runs on a schedule, as the person who set it up.

A recurring job repeats a request on a schedule: it either starts a session with instructions for the agents, or posts a message into an existing session. Add one from a project's Recurring jobs section: name it, say what the agents should do, and pick when it runs (every weekday, every week on a day, every month on a date, or a custom schedule) and the time zone.

A job runs as the person who added it and counts against their limits. Show its runs lists every run and whether it succeeded; a run in progress can be stopped. Any member may schedule jobs on the projects they can see; jobs that run commands on the server are for administrators only.

When a job meets a check only a person can pass

A job that drives a website can meet a captcha or a "verify you are human" page. It never tries again and never gets around it: it stops, and the check shows up in your inbox under Checks only you can pass, and as an alert. Open it and you see the page the job is waiting on as a live picture: click on it, type into the box, then press Done: I solved it and the job carries on from that same page, or Give up and it ends.

Only type what you would type on the site named at the top of the page. An administrator can act on every check; when a check belongs to a project, so can the people who work in that project. Every look and every action is in the audit log, without what was on the page or what you typed. On the command line, evriq assist list shows the checks waiting and evriq assist done <id> or evriq assist abort <id> answers one.