Scheduling & Jobs

Run work later or in the background: schedule.* creates timed jobs, and jobs.* runs and broadcasts subflows at a controlled pace.

Scheduled flows (`on schedule`)

The simplest scheduling is a cron-triggered flow:

flow daily_digest on schedule "0 9 * * *" {
  send.text("☀️ Good morning!", chat_id: shared.group_chat_id)
}

See Triggers for the cron format. Scheduled flows have no chat in scope — always pass chat_id.

Create a one-off or recurring job programmatically (by delay, datetime, or cron). When it fires, it runs the named trigger.

let { task_id } = schedule.create(
  trigger_name: "reminder",
  params: { delay: "1h" },
  user_id: user.id
)
set { user.reminder_task = task_id }

Outputs: task_id, scheduled_for, error_text.

Cancel a scheduled job by its id:

let { cancelled } = schedule.cancel(task_id: user.reminder_task)

Param	Type
`task_id!`	String

Outputs: cancelled, error_text.

For work that fans out across many users, use the jobs.* family. These run a subflow on the worker pool at a controlled pace.

Enqueue a one-off subflow execution:

let { handle } = jobs.run()

Run a subflow for each user in the audience, paced to respect rate limits:

let { handle } = jobs.broadcast()
set { shared.last_broadcast = handle }

Check progress by handle:

let { status, progress } = jobs.status(handle: shared.last_broadcast)
send.text(`Broadcast status: ${status}`)

jobs.cancel(handle: shared.last_broadcast)

tip

For sending the same message or media to your whole audience, the telegram.broadcastMessage / broadcastMedia / broadcastFlow recipes wrap this with a friendly signature.