Skip to content
Fork Docs
Guide v1

Scheduled Tasks

Fork can store scheduled work through its AI scheduling tool when enabled/authorized, and administrators can manage supported tasks in the dashboard. The public command registry does not contain a standalone slash scheduling command; do not invent one from an internal tool name.

Two entry paths

Section titled “Two entry paths”
  • Ask in an eligible AI channel with an explicit time/delay and prompt.
  • Use Scheduled Tasks in the authenticated dashboard for the selected server.

The tool path validates the request and stores the current server channel as destination. A channel mentioned in prose is not necessarily the selected destination.

Confirm persistence

Section titled “Confirm persistence”

Wait for a successful scheduling result and retain its task ID where shown. A conversational promise is not proof of a stored task. Inspect the dashboard before submitting another reminder after an error.

This edition does not advertise recurring cron scheduling as a general public interface. Read Reminders, Delivery Behavior and Managing Existing Tasks for the supported boundaries.