Skip to main content

Creating a scheduled job

Open /scheduler/new to start. The wizard collects four things in order: name, schedule, executor, retry policy.

1. Name and tags​

  • Name is required and shows up everywhere this schedule appears. Make it scannable.
  • Description is optional but recommended — your future self / teammates will thank you.
  • Tags group related schedules and let you filter the list view.

2. Schedule​

Pick one schedule type. The form below adapts.

  • One time — pick a date and timezone. The run fires once, then the schedule is COMPLETED.
  • Fixed interval — Every 30 minutes style. Combine with Start date and End date to bound the window.
  • Cron — 0 9 * * MON-FRI style. Cron-strings honor the timezone you pick; preview will show local times.
  • RRULE — RFC 5545 recurrence rule. Use this for "every other Monday" or "third Friday of the month."
  • Windowed — define one or more time windows (MON 09:00–17:00, WED 09:00–12:00). Schedule only fires inside those windows.

You can attach a business calendar to skip holidays, and pick a misfire policy for what to do if the system was offline when a run was due (FIRE_IMMEDIATELY / FIRE_NEXT_VALID / SKIP / COALESCE).

The Schedule preview panel shows the next 10 fire times for your chosen pattern. Use it to sanity-check before you save.

3. Executor​

Two ways to define what runs:

  • Pick an Action — start typing in the Action picker. The executor is auto-generated from the Action.
  • Configure manually — pick an executor type:
  • Webhook — POST to a URL with optional headers and a JSON payload template
  • GraphQL endpoint — call an internal GraphQL operation through the workspace GraphQL endpoint
  • the event bus topic — publish a message to a the event bus subject
  • GraphQL — execute a named GraphQL operation

The payload template field supports {{variables}} — values from the schedule's metadata and execution context get substituted at run time.

Secrets entered in this section are stored encrypted and never shown in plaintext after save.

4. Retry policy​

  • Max retries — how many extra attempts after a first failure
  • Retry delay — seconds to wait between attempts
  • Backoff strategy — FIXED, LINEAR, EXPONENTIAL, or EXPONENTIAL_WITH_JITTER
  • Auto-disable after — after N consecutive failures, the schedule auto-disables. Set to 0 to never auto-disable.
  • Circuit breaker — once N failures happen in a window, future runs short-circuit until cooldown.

Save​

Saving creates a DRAFT schedule. Click Activate on the schedule detail page (or set Activate immediately in the wizard) to start the schedule running. You can pause and resume any time.