Recurring workflows

Ask Tasuku in Slack to repeat a question, research request, or build at an interval of five minutes or longer. Tasuku creates a durable schedule, runs the first occurrence immediately, and delivers each result to the selected Slack channel.

Supported work

• Question runs a bounded agent request with the configured runtime.
• Research uses configured remote MCP servers, requires source-backed output, and can publish a private HTML artifact.
• Build targets an explicit GitHub repository and follows the normal plan approval boundary before implementation.

Results can use Markdown or plain ASCII. A research schedule may include a completion condition. Build schedules do not support automatic completion; stop them manually when the work is no longer needed.

Scheduling behavior

Tasuku uses fixed delay after each terminal occurrence:

• no overlapping occurrences;
• no catch-up burst after downtime;
• the next run is scheduled only after the current occurrence finishes;
• transient failures use the normal durable retry path;
• three consecutive terminal failures pause the schedule.

This keeps a slow run from creating a queue of stale duplicate work.

Operate a schedule

Open Recurring workflows in the dashboard to inspect status, interval, next run, active occurrence, and consecutive failures. Available actions include:

• Run now — request one immediate occurrence when no run is active;
• Pause — retain the schedule without starting new occurrences;
• Resume — make a paused schedule active again;
• Stop — end future execution;
• Change interval — apply a new delay to future occurrences.

The Slack thread remains the delivery context. Occurrences, workflow runs, and agent tasks remain available in Tasuku for audit and diagnosis.