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. Every workspace also has a Schedules page (Schedules in the sidebar) that lists all schedules in the workspace, including one-shot schedules Copilot created without saving a workflow. Dashboard Copilot can propose a schedule on the Confirm card. Recurring Copilot schedules start paused: a test run runs first, then you click Enable schedule. Copilot never enables a schedule by itself.

​
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

Schedules use structured recurrence only. There is no cron syntax.
  • every N days at a local time
  • every N weeks on selected weekdays at a local time
  • every N months on a calendar day (1–31 or the last day of the month). Shorter months clamp to the last day (for example, day 31 becomes 30 April or 28 February).
  • once, at a local date and time. After that run the schedule is completed and does not fire again.
Fetch Hive calculates the next run in the schedule timezone. This keeps local run times consistent across accounts.

​
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. If scheduled execution is delayed by downtime or worker recovery, Fetch Hive launches only the latest due occurrence instead of replaying every missed occurrence.

​
Lifecycle

A schedule can also complete or pause itself:
  • Expires at — after the last valid occurrence on or before this time, the schedule is completed.
  • Max runs — after that many scheduled launches, the schedule is completed.
  • Consecutive failures — three launch failures in a row pause the schedule. An inactive deployment or a credit cap pauses it immediately.
Completed schedules cannot be resumed. Create a new schedule if you need the same automation again.

​
Run now

Use Run now to fire the schedule immediately through the same path a real occurrence uses. This works on active and paused schedules. It does not change the next run time, run count, or status. The run still appears in workflow logs as schedule-triggered. Copilot-created schedules are labeled with their source so you can see they were created by Copilot rather than from the Studio dialog.

​
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. Completed schedules cannot be resumed. 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.