Skip to main content
Scheduled tasks are project-level triggers that either enqueue work into room queues or start containers on a schedule. A scheduled task uses a ScheduledTaskSpec file. The spec chooses exactly one target: queue or container. The room is selected when the task is created, not inside the spec.

​
Create a scheduled task

This creates a scheduled task in the active project that enqueues work into the support-jobs queue in the support room. The payload is a JSON object. For MeshAgent queue consumers, that can include the same structured prompt, content, and path fields supported by meshagent room queue send. Example:
To start a container instead of writing to a queue, use container:

​
Inspect and manage scheduled tasks

List tasks:
Update a task:
List runs for a task:
Delete a task:

​
Where to manage them

  • Use MeshAgent Studio when you want the main UI flow.
  • Use the CLI when you want quick setup or automation.
  • Use the REST API when you need programmatic provisioning.
Schedules must be at least 15 minutes apart. If you want a recurring turn owned by one agent inside a service manifest, use agents[].heartbeat instead of a separate scheduled task.