Put a flow on a schedule

A schedule runs a flow on chosen profiles at a chosen hour without anybody pressing start. The path is RPA Plus in the left column, then the clock button in the flow's row. People use it for the daily warm up that otherwise gets done by hand at nine every morning.

It runs while open

Nothing is installed into the system, so a run cannot happen on a closed laptop. The window says this before you fill anything in, rather than after the first missed morning.

The schedules live in the account, so the same plan is readable from another computer as well.

Add a schedule

Every schedule belongs to one flow, and the same flow can carry several.

1
Open the automation screen
The RPA Plus tab in the left column.
2
Press the clock on the flow
The button in that flow's row in the list.
3
Choose How often
The picker at the top of the schedule window.
4
Pick the profiles
The list under Which profiles to run, in the same window.
5
Press Add schedule
The button at the bottom of that window.

Three ways to repeat

Every day at a time you set, on chosen days of the week at that time, or every few hours. The hours are counted in your own local time, so a change of season does not shift the hour.

How many profiles start together is your choice too, and it sits next to the profile list.

One machine runs it

A schedule that arrives from the account is off on this computer until you say Run here. Two open machines firing the same run would double the work and the traffic.

Pausing is the shared decision and travels everywhere, so a schedule paused in one place stays paused.

Missed runs are not made up

After a closed night you are told how many slots passed, and none of them fire late. A burst of runs at once is exactly the pattern a site reads as a robot.

When a slot is skipped

Three reasons, and each one is named where you can read it: every profile of the schedule is already open, the previous run of that flow is still going, or the program has no active subscription.

A slot more than half an hour late is not fired at all, it is counted as missed.

Reading the outcome

Each schedule shows its next slot, the last result and how many runs were missed. All schedules gathers every one of them, soonest first.

The outcome is stored as a neutral mark and put into words where it is shown, so it reads the same on another computer and in another language.

What this does not do

It does not install a service in your system. A closed program means no runs.
It does not catch up on what was missed. Slots that passed are counted and reported, not fired late.
It does not run the same schedule on two computers at once. One arriving from the account waits for you to switch it on here.

Where this is decided

Each claim above is one place in the code and one stand.

The schedule fires on time and does not produce a burst of runs after sleep: apps/desktop/test/schedule-runs.js
A schedule arriving from the account is switched on for this machine by hand: apps/desktop/test/расписание-включается-здесь.js
The outcome survives a change of language and a move to another computer: apps/desktop/test/schedule-result-language.js
Schedules live in the account, and who may change them is settled there: apps/server/test/schedules-shared.js

Questions

Can it repeat every ten minutes?: No. The shortest repeat is every few hours; the other two are a daily time and chosen days of the week.
The run was skipped and I do not know why.: The reason is written next to the schedule: profiles already open, the previous run still going, or no active subscription.
My laptop was closed all night.: Nothing ran, and you are told how many slots went by. They are not fired afterwards on purpose.
Does the result read the same in another language?: Yes. It is kept as a neutral mark rather than as a sentence, and turned into words only where it is shown.

Next to this

Try it on one flow

The free plan gives two profiles, with no time limit and no card.

Download ARMANOS Knowledge base