Scheduled tasks
Lesson 7 of 10 · 3 min 36 s. Set up recurring work once and let it file itself. Create an automation that checks an app for accessibility problems every morning, say when and where it runs and what it does, try it at once with Run now, read what the task it filed did, and look back over its runs.
Before you start
- You have done Keeping the list in order and are signed in to the console.
- A project connected to Jaah, picked on Tasks. The example is TimeSaver, a time-tracking app for small teams.
- Tests in the project, so the agent can make sure the app still works after it fixes something.
Steps
- Click Audit, in the sidebar, then the Automations tab. Automations lists the work that runs on its own: each job with where it runs, when, and how its last run went.
- Press + (New automation). The wizard has three steps, named across the top: When, What and Name. On When, Schedule is already chosen. Press Edit beside it. Every day is already picked, so set only the hour: 6, before anyone starts work. Under the schedule, the console shows when the next run will be. Press Next.
- On What, Action is already Task. Under Target, open Run in projects and pick the TimeSaver app, so the work happens in its code.
- Below it, say what you want done, in your own words, the same way you'd write a new task: Check the app's pages for accessibility problems, and fix the ones you find. Unattended is already chosen, so the agent decides everything itself; nobody is around at six in the morning to answer a question. Press Next.
- On Name, the console has filled in a name from the first line of what you wrote. Give the job a name the team will recognise instead: Morning accessibility check. Press Create. The job's own page opens.
- Press Run now. The job runs straight away, exactly as it will every morning, without waiting for six. The console confirms it's running, and the run appears under Runs once the job has filed its task.
- Go back to Tasks. The job has filed a task of its own, with its instructions as the request. From here it's ordinary work, handled like any task you file yourself, with the same checks before anything is delivered.
- When it's finished, open the task and go to Details. Under Outcome, the agent says which problems it found, what it fixed, how it made sure the app still works, using TimeSaver's own tests, and anything it left for a person to decide.
- To look back over a job, open it from Automations and go to Runs. Each run is listed with when it fired and what it did, here the one task it filed. A morning when it did nothing stands out at once, and so does a run that filed something nobody expected.
What you learned
- Audit, then Automations, in the sidebar, opens Automations: the work that runs on its own.
- A new automation takes three steps: when it runs, what it does and where, and its name, then Create.
- Run now starts a job at once, so you can see what it does without waiting for its schedule.
- The job files an ordinary task, followed and read like any other, and its Runs tab lists every run with what it did and when.
Next
Next lesson: Adding a project. Previous: Keeping the list in order.
Related: