Tasks and scheduling

A Task associates a Job with a schedule and optional settings overrides. You need permission to manage Tasks; running the resulting work also depends on the project’s state and available capacity.

Create a Task

1. Open Tasks / Scheduler in the project.
2. Create a Task and select its Job.
3. Choose the calendar type and timezone.
4. Review the upcoming-date preview.
5. Review inputs and settings overrides.
6. Save, then explicitly activate the Task when ready.

Saving a Task and activating it are distinct decisions. Confirm the displayed active state.

Calendar choices

Use a one-off calendar for a specific date and time. Use the recurring calendar for repeated launches. The schedule editor offers presets and controls for minutes, hours, days and months, with a readable description. Use its upcoming-date preview as the authoritative check. Advanced editing retains custom expressions without silently replacing them. The underlying cron dialect uses five numeric fields:

minute hour day-of-month month day-of-week

For example, 0 9 * * 1-5 represents a weekday 09:00 schedule. Check the actual preview for the selected timezone before activation. Do not paste a six-field expression with seconds or a different recurrence format.

Timezone matters around daylight-saving changes. Use previewed dates to check the next occurrences; do not assume that a fixed local hour always has the same UTC offset.

Overlap and missed occurrences

Open Advanced scheduling to review the overlap choice before activating a frequent Task. If an earlier execution is still active, the selected policy determines how a later occurrence is handled. Review catch-up behavior for missed scheduled times as a separate choice.

Use occurrence history to distinguish a scheduled occurrence from the Session it may produce. A planned time is not a promise that a Robot starts at that instant. Queuing, project dispatch and capacity can delay execution.

Change or pause scheduling

Disable a Task to prevent future automatic launches under its schedule. This does not automatically stop Sessions that were already accepted. Use Session controls for those.

When changing a Task’s Job or settings, review the next-date preview and save explicitly. Existing accepted Sessions retain their captured settings. Follow Session supervision to inspect or stop existing work.