Skip to main content
Use schedules when a workflow deployment should run automatically, such as a daily research search or a weekly reporting workflow. Schedules are managed from the workflow deployment detail page. Open a deployment, click Schedules, then create or edit a schedule for one of the deployment variants.

​
What a schedule stores

A workflow schedule stores:
  • the deployment variant to run
  • a schedule name
  • active or paused status
  • recurrence settings
  • timezone
  • optional callback URL for signed completion delivery
  • saved Start input values
The schedule runs the published deployment variant, not the mutable workflow draft. The saved input values are used each time the schedule fires. When a Start input is configured as Array, the schedule form stores a native JSON array. Enter the value as valid JSON, such as ["one", "two"] or [{"url":"https://example.com"}].

​
Supported recurrence

The first schedule builder supports:
  • every N days at a local time
  • every N weeks on selected weekdays at a local time
Fetch Hive calculates the next run in the schedule timezone. This keeps local run times consistent across accounts and avoids requiring raw cron syntax.

​
Scheduled run behavior

Scheduled runs reuse the same execution path as normal workflow deployment invokes. That means:
  • the deployment version snapshot stays intact
  • workflow step settings, including search language settings, are preserved
  • billing and hosted LLM credit checks still apply
  • personal credentials and deprecated model checks still apply
  • workflow concurrency limits still apply
  • optional callback delivery runs when the schedule completes or fails
  • runs appear in workflow logs
Scheduled runs include metadata marking them as schedule-triggered, including the schedule id, schedule name, and scheduled time. They are attributed to the workspace Default API key in workflow logs and include the saved schedule inputs in the request payload and trace details.

​
Pause, resume, and delete

Pause a schedule when it should stop launching new runs without deleting its configuration. Resume recalculates the next run time from the current time. Deleting a schedule archives it, so past schedule run history can still be audited internally.

​
Notes

Schedules currently apply only to published workflow deployments. Draft workflow scheduling and dynamic date variables for saved inputs are not part of this version.