Scheduled tasks

A scheduled task runs a saved workflow, or a prompt you type, on a schedule you set. A daily briefing, a weekly report, a one-time reminder for tomorrow afternoon: set it once and Arro runs it on time. Scheduling starts on the Plus plan. On Free the Scheduled page shows what scheduling does and a link to upgrade, in place of the list. Open Scheduled in the left sidebar to create and manage them, in either the desktop app or the web workspace. Filter the list by status to find a schedule. If nothing matches, choose Clear filter to see all schedules again.

​

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, so you can check the timing before you save.

​

Frequency

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: clearly safe actions run, and anything unsafe 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. 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 one-time task that is Completed or Expired cannot run again, so its menu offers only View last run and Delete. Create a new task to schedule it again.

​

Working through a task board

A schedule that runs a workflow bound to a board works through the tasks waiting in that task board’s pick-up list. It runs on your computer, as you, so several people can each point one at the same task board and share the work without ever picking up the same task.

​

Usage and limits

Scheduled runs draw on your workspace’s monthly usage, the same usage as chat, automation, and voice. If the workspace’s usage is exhausted when a run is due, or the person who created the schedule has reached an admin-set limit, that run is skipped. Your plan sets how many scheduled tasks a workspace can hold. That number is a total rather than a monthly quota, so a completed schedule keeps its place until you delete it. See Plan limits.

​

Related