Skip to main content

Workflow scheduled tasks

Scheduled tasks let AI Agent automatically run saved workflows on rules you set, without clicking Run each time. Each trigger creates a normal task — view progress and results in Tasks & monitoring.

Open scheduled tasks page

  1. Start new control center, open AI Agent
  2. Top navigation "Scheduled tasks"

Page includes: New, Refresh, Search, and list of all rules.

Create a scheduled task

Click "New scheduled task", fill in:

FieldDescription
Task nameRecognizable name, e.g. “Daily check-in”
WorkflowWorkflow to run (search supported)
Schedule typeSee table below
Max executions0 = unlimited; rule auto-pauses when limit reached
When device busySee Device busy policy
Startup paramsOptional JSON passed to workflow (same as manual run params)
Target devicesBy device or By group multi-select; resolved to device list on submit

Schedule types

Same meaning as control center scheduled task Time:

TypeDescriptionExample
DailyOnce per day at hour:minute:secondDaily 9:00:00
Interval minutesTrigger again N minutes after last successful triggerEvery 5 minutes
Interval secondsTrigger again N seconds after last successful triggerEvery 30 seconds
No catch-up

If AI Agent process restarts or stops, missed triggers during downtime are not run in bulk after recovery. Interval rules continue from last run time (or when created/re-enabled); daily rules trigger at next matching time only.

Device busy policy

When a device is running another workflow task:

PolicyBehavior
Skip (default)Device skipped for this trigger; others run normally
Stop current task then runCancel running task on that device, then start this workflow

If all target devices are skipped, trigger fails; reason recorded in Recent error column.

After save

  • New rule defaults to Running (active)
  • List shows: name, workflow, schedule summary, device count, status, execution count, last run time, etc.

Common list actions

ActionDescription
EditChange name, workflow, schedule, devices, etc.
Run nowTrigger immediately without waiting for schedule (debugging)
PauseNo auto trigger while paused; can Resume
DeletePermanently delete rule
SearchFilter by task name, workflow, status, source, etc.

Identify source in task panel

Tasks from scheduled triggers show source "Scheduled task" in Tasks & monitoring; if the rule has a name, it appears too (e.g. Scheduled task · Daily check-in).

Other sources:

Source labelMeaning
AI sessionScheduled from chat, or Run on workflow card in chat
Workflow editorEditor Trial run / Run
Scheduled taskAuto schedule described here
Manual executionOther API trigger (uncommon)

Task list collapsed by default; click a row to expand per-device execution.

Usage notes

  1. AI Agent must be running Schedule runs inside AI Agent process; no trigger if process is down. Usually kept alive by new control center — do not leave AI Agent closed long term.

  2. Workflow must exist and be runnable Sealed workflows (.spk +.spl) must be within validity; otherwise trigger fails, error in Recent error column.

  3. Devices & licensing Same as manual run — complete Prerequisites & licensing (USB license, IPA, etc.).

  4. Concurrency One device runs one workflow task at a time; multiple devices can run in parallel, limited by Settings → Max devices per task.

  5. Same as manual run Scheduled trigger uses same chain as Run / Trial run — steps, variables, license checks identical; does not consume chat LLM Tokens.

FAQ

After pause and resume, does it run immediately?

Interval rules recalculate interval from current time on resume — no burst catch-up from pause period. Daily rules wait for next matching time.

If group membership changes, does the scheduled task follow?

If you chose By group at creation, the saved device ID list is fixed at that moment. Later group changes do not sync to existing rules — edit the scheduled task and re-select, or use By device.

What happens when execution limit is reached?

Rule auto-changes to Paused. Click Resume to continue (if still at limit, edit to raise limit — current logic uses cumulative execCount; edit does not reset count; create new rule or wait for future reset support).

Next steps