Recurring

Set a task once, run it forever, until you pause it.

A recurring task is a template that fires on its own at the cadence you set: daily at 9am, every six hours, every Monday morning. Each scheduled run creates a fresh task on the Work board, with a fresh deliverable for review. You set up the template once; Busy Bee handles the rhythm.

This page is a short overview. For the full deep-dive (schedule shapes, lifecycle controls, best practices, and example templates), see Recurring (Features).

Two schedule shapes

• Daily - run at a specific clock time, every day or on a subset of weekdays. Use for human-cadence work (briefings, summaries, planning prep).
• Interval - run every N minutes/hours/days from the last run. Use for monitoring and polling (inbox sweeps, API polling, status checks).

Both honor your workspace timezone.

How recurring fits into Tasks

Each recurring run is a regular task, same status badges, same approval controls, same place on the Work board. The only thing different is how it got there. The recurring template is the recipe; the runs are the meals.

A run's task knows which template produced it, so you can jump from any run back to the template, edit the recipe, and the next run picks up your changes.

Lifecycle at a glance

• Pause - stops new runs.
• Resume - turns it back on.
• Run now - fires an immediate one-off run outside the schedule.
• Edit - change the prompt, agent, schedule, or context.
• Delete - removes the template; past runs stay in your history.

What's next

For the long-form treatment, schedule details, good first uses, pairing with workflows, head to Recurring (Features). For one-shot future runs (not on a cadence), see Scheduling next.