Recurring
Run agents and tasks on a schedule.
Set work on a schedule. Your team handles the cadence so you don't have to.
A recurring task is a template Busy Bee runs on its own at the interval you set, every weekday at 9am, every six hours, once a month on the 1st. Each run creates a brand new task on the Work board, executed by whatever agent the template specifies, with the deliverable surfaced for review just like a one-off request. You set it up once; the team handles the rhythm.
Where to find it
Open the Recurring Tasks page from the dashboard (sidebar → Recurring Tasks). The page lists every template you have set up, when each one last ran, when it'll run next, and whether it's currently active or paused.
📸 Screenshot: the Recurring Tasks page with a few templates listed, each showing last-run and next-run timestamps.
Two schedule types
When you create a template you pick one of two schedule shapes:
- Daily - runs every day (or on a subset of weekdays you choose) at a specific clock time. Use this for anything tied to a human cadence: morning briefings, end-of-day summaries, Monday-morning planning prep.
- Interval - runs every N minutes, hours, or days from the last run. Use this for monitoring and polling: "check the support inbox every 30 minutes," "ping the analytics API every 6 hours."
Both schedule types respect your workspace timezone, so 9am means 9am wherever you are.
Setting one up
Creating a recurring template is the same flow as creating a regular task (pick an agent, write the request, attach any context) with one extra step at the end where you choose the schedule.
📸 Screenshot: the recurring task creation modal with the schedule selector visible.
A couple of practices that pay off:
- Write the request the same way you'd write it as a one-off. Recurring templates re-use the same agent, prompt, and tools every time; clarity in the prompt now saves debugging later.
- Pin the agent. If the template will be used by your Researcher specifically, assign that agent directly rather than letting Queen Bee re-route each run.
- Include "what changed since last run" if relevance is time-sensitive. The agent has memory of past runs but it's helpful context.
Lifecycle controls
Every recurring template has four controls:
- Pause - stops new runs without deleting the template. Resume any time.
- Resume - turns a paused template back on.
- Run now - triggers an immediate run outside the schedule, useful for testing or one-off catch-ups.
- Edit - change the prompt, agent, schedule, or context. Edits take effect on the next scheduled run.
Delete a template entirely if you no longer need it; past runs remain in the Work history.
📸 Screenshot: the row-level Pause / Run now / Edit menu on a recurring template.
Where runs show up
Each scheduled run creates a fresh task on the Work board with the same status badges and approval controls as any other task. If you want a quick "show me everything this template has produced" view, the Recurring Tasks page links each template to its history.
Good first uses
- Daily standup digest - Daily, 8:45am weekdays. Agent: PM. "Summarize what shipped yesterday across active projects and what's queued for today."
- Weekly investor update - Daily on Fridays at 4pm. Agent: Writer. "Draft this week's investor update from the latest project status."
- Hourly support sweep - Interval, every 60 minutes. Agent: Researcher. "Check the support inbox; flag anything urgent."
- Monday planning prep - Daily, Monday at 7am. Agent: PM. "Pull the team's open tasks and propose a priority order for the week."
What's next
Recurring pairs well with Workflows: schedule a workflow template the same way you schedule a single task, and Busy Bee runs the whole multi-step sequence on cadence.