Deploy on a schedule

Run a declared version automatically on a calendar schedule.

Deploy is scheduling; Run is manual execution. A deployment points to one declared version, source bindings, incremental-task choices, and a calendar rule.

workspace.deploy(
    deployment_id="news-monthly",
    pipeline_id="news-events",
    version_id="v2",
    schedule="monthly",
    start_date="2026-07-30",
    start_time="12:00:00",
    timezone="America/New_York",
    sources=["headlines"],
    incremental_tasks=["group-events"],
    max_cost_usd_per_run=10.0,
)

Calendar semantics

• Daily: every day at the selected local time.
• Weekly: the weekday established by the start date.
• Monthly: the day established by the start date.

If a monthly day does not exist, the run uses that month's final day and returns to the original day in the next longer month. A July 30 schedule therefore runs on February 28 or 29, then March 30—not every 30 elapsed days.

Observe deployments

Scheduled runs create ordinary sessions. Open the version to see active and past sessions, or query them through the API. A failed run does not alter the declared schedule.