Skip to main content

Scheduler

Scheduler is where you set up agent runs (and scheduled social posts) to fire on a cadence — daily standups, weekly digests, "run the social-post agent every Tuesday at 10am" — instead of triggering them manually. Each schedule is workspace-scoped and persists until you delete it.

📷 Screenshot: Scheduler tab with single-occurrence and recurring sections.

Two sections​

Schedules are grouped by shape:

  • Single Occurrence — runs once, at a specific date and time.
  • Recurring — runs on a frequency (daily / weekly / monthly / yearly) with an interval ("every N units") and an optional end date.

Each schedule renders as an accordion. Collapsed, you see the schedule's name, type, next-run timestamp, last-run outcome (succeeded / failed / cancelled), and a small action menu. Expanded, you see the recent run history (last 25), the underlying parameters, and per-run links into the execution detail view.

Creating a schedule​

Click + New Schedule to open the dialog. Step through:

  1. Type — Agent Run or Social Post. Agent runs invoke a chosen agent with whatever parameters you supply; social posts queue a draft to publish on a connected platform.
  2. Agent (for Agent Run) — pick from the list of workspace agents. The "Don't see your agent?" link drops you into Agent Builder so you can create one and come back.
  3. Platform (for Social Post) — LinkedIn, Twitter, Facebook, Instagram, Threads, YouTube, TikTok, or Reddit.
  4. Recurrence — toggle off for one-time runs, on for recurring. With recurrence on, pick the frequency (daily / weekly / monthly / yearly), the interval (every N units), and an optional end date.
  5. Scheduled At — the first run time. The dialog reads your browser timezone and shows the local equivalent so you don't have to convert.
  6. Parameters — any agent-specific inputs (depends on the agent's parameter shape).

Save commits the schedule, which immediately appears in the right section.

Editing, cancelling, retrying, deleting​

The action menu on a schedule's accordion exposes:

  • Edit — re-opens the same dialog with the current values pre-filled. Editing a recurring schedule applies to future runs; runs already in flight or completed aren't affected.
  • Cancel next run — skips the next scheduled fire (useful for one-off pauses without disabling the whole schedule).
  • Retry — re-runs the most recent execution if it failed. Picks up the same parameters.
  • Delete — removes the schedule. Past runs stay in your execution history for the audit trail; only the schedule itself goes away.

Filtering​

The filter bar above the list slices schedules by date range — useful when you want to see only schedules that fire this week, or only schedules that were active in a given month. The "Show all schedules" link clears any active filter so you don't have to remember what you set.

How schedules fire​

Each schedule writes to Firestore with a next-run timestamp; a Cloud Scheduler job polls and dispatches the actual agent run when its time comes. While running, the schedule's execution shows up under Active Agents → Running; once finished it moves to the schedule's accordion as the new "last run", and into Active Agents → Recent for the workspace-wide audit view.

Inbox surfaces upcoming and recently-fired schedule items under the Scheduled filter — clicking that filter in the Inbox sidebar links straight back here.