Scheduled runs

Scheduled runs use the same isolated harness path as chat. The difference is the trigger and, optionally, where the final response is delivered.

Monitor a schedule#

The Schedules tab shows definitions from the pinned schedules.toml and the calculated next fire time. Disabled agents are skipped.

Aleph checks enabled agents hourly and prevents the same due occurrence from running twice.

Run now#

Use Run now to execute one schedule immediately. This is the fastest way to test its prompt, configuration, and delivery without changing its recurrence.

Understand delivery#

A targeted schedule uses deliverTo.bindingId. Without a target, Aleph posts only to the configured Discord Schedule channel. No Schedule channel means the run can succeed while delivery records an actionable error.

Silent assistant results are stored but not posted. Partial output from a timed-out run is not treated as a completed deliverable.

For the bundle syntax, see Schedules.