edisyl schedule

From the CLI, ask and task become schedules with --cron "<expr>" (30-minute minimum interval) or --at <RFC3339>. --name is an optional human label. The create command prints a schedule id: every command below takes that id, not the name.

edisyl schedule list [--pack <pack>]     # ids, labels, when they run, last/next run
edisyl schedule view <schedule-id>       # when it runs, brief, recent runs
edisyl schedule trigger <schedule-id>    # run it now; returns an actionId to follow
edisyl schedule runs <schedule-id>       # run history
edisyl schedule pause <schedule-id>      # stop firing, keep it
edisyl schedule resume <schedule-id>
edisyl schedule delete <schedule-id>     # disables it; --force removes it outright

delete without --force does not delete anything: it disables the schedule, which stays listed with its history and can be resumed. --force removes the row for good, and the server refuses that once the schedule has ever run.

Each fire creates that verb’s own Action: a scheduled ask answers, a scheduled task works, and schedule list/view report which verb a given row runs. See Scheduling recurring work for why only ask and task are schedulable (a brief carries their whole request; teach and import need a file or target they don’t have at schedule time).