Skip to content

Schedule recurring work

Test a task once before arranging it to run on a schedule.

Steps

  1. 01Verify a single run
  2. 02Set frequency and time zone
  3. 03Check the computer and access
  4. 04Review runs and deliveries

01 Verify one run first

Choose an employee task or workflow that has passed a trial. Complete the inputs and delivery requirements. Resolve problems with one run before scheduling repeats.

02 Set the schedule, time zone and scope

Choose the work in automation, set its schedule and time zone, and check the next run time. Confirm the workspace so a team schedule is not accidentally created in personal space.

03 Keep execution requirements available

The computer, RunTeams, agent, provider usage and access must meet the task’s requirements. Models and external services may need a network connection. Work does not move to a cloud computer when yours sleeps or becomes unavailable.

04 Review each run and delivery

Check timing and inputs before enabling the schedule. Review the work record and actual delivery after it runs. Resolve failures and pause the schedule if necessary. Editing or re-enabling a schedule does not repeat completed tasks or backfill missed periods.

Instructional example

Example: a weekly project update

Every Monday morning, read authorized project materials and summarize progress, risks and unresolved questions. List missing inputs rather than inventing progress.

Active schedules and execution requirements

Free allows three active schedules shared across employees, workflows and recurring automations. Pausing releases a slot; one-off manual tasks do not use a slot. Provider usage, concurrency and computer capacity still apply.