Ask Arro to schedule it
You do not have to open a dialog. Ask Arro out loud or in chat, for example “run my weekly report workflow every Monday at 9” or “remind me tomorrow at 3pm to submit my timesheet”. Arro can also pause, edit, and delete your schedules when you ask.Create a scheduled task
Click New scheduled task and fill in the dialog.
A prompt is the same kind of request you would hand Arro as a
background task. As you fill the dialog in, it previews the
next runs under Repeat, so you can check the timing before you save. Pressing Create marks
anything missing in red.
Repeat
Pick the date and time first, then how it repeats. Times go in five-minute steps.
Every month skips any month without that day, so the 31st runs in seven months a year and the
30th never runs in February. To run in every month, choose Last day of every month.
With End repeat set to On date, the last run is on or before that day. The task then shows
as Completed.
Schedules are timezone-aware, so a run fires at the local time you set wherever the desktop app is
running. A recurring schedule can run at most once every five minutes.
If your computer was off
A recurring run can be missed if your computer was off or asleep, Audimate was closed, or you were working in another workspace when it was due.
Anything older than 24 hours is skipped either way.
Statuses
A missed run shows in the Last run column on the Scheduled page, with the reason on hover.
A schedule that fails five runs in a row is disabled automatically, so a broken task does not
keep consuming your workspace’s usage. Fix what is blocking it, then resume it from its menu.
Approvals
A scheduled run has nobody at the screen, so it never shows an approval card, not even if you have set Arro’s approval mode to Manually approve. A card nobody can answer would stall the task until it timed out. Every gated action goes to the safety check instead. An action runs unless it looks dangerous, and anything dangerous is declined, so the run works around it or stops and records what was blocked. The run’s history shows which way each one went. A folder the run asks for, such as the Desktop it saves to, is checked once and then stays open to that run. Put the folders and sites a schedule needs on your Allowed folders and Allowed sites lists before you rely on it, because anything already there never needs a check at all. A run that keeps getting blocked fails, and five failures disable the schedule. For the same reason a scheduled run never waits for you to clear a sign-in, a CAPTCHA, or a two-factor prompt. It stops, records what blocked it, and ends. If a schedule needs a site you are signed into, sign in once in Arro’s own browser under Arro → Browser → Sign in.Manage a scheduled task
Open the ⋯ menu on any row.
A task that is Completed or Expired cannot run again, so its menu offers only View last
run and Delete. That covers a one-time task after its run, and a repeating task once its end
date passes. Create a new task to schedule it again.
A task on every run
When the workflow’s playbook mentions task board fields, the dialog asks for Task details in place of instructions. Each scheduled time adds a task with those details to the task board’s pick-up list, and it runs on your computer, as you. The Last run column then shows Added a task to its task board. Any other playbook runs the workflow once. See What a schedule does. The dialog asks for each field the playbook names that is on the task board’s New task form, and for any other field the task board requires. A named field kept off that form is what the run fills in, so it is not asked. Attachment fields are never asked. Every detail needs a value, because nobody is there to answer when the run starts. A checkbox can be left unticked unless the task board requires it. When the playbook doesn’t name the task board’s title, the schedule doesn’t ask for it. Each task is named after the schedule and the date and time it ran. If the playbook later names a field the schedule has no value for, the schedule stops instead of running, shows Needs details, and sends you a notification. Edit it, fill in the new details, and save to start it again.Usage and limits
Scheduled work draws on monthly usage. Free usage belongs to you; paid workspaces share an allowance. A run is skipped when the available usage runs out or its creator reaches an admin-set limit. Scheduled workflows also need an available workflow run. See plan limits for schedule capacity and included features. When Free’s included runs are used up, workflow schedules turn off and show: “Your included Free workflow runs have been used. Upgrade to run workflows again.” After upgrading, resume recurring schedules. Create a new task for a one-time schedule whose time has passed.Related
Task boards
Tasks a schedule can work through.
Work
Everything Arro can do for you, in the background or on repeat.
Desktop app
Schedules run from here while the app is open.