Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<@ULVA73B9P> is this part of the docs outdated? I've read the "schedule" field was replaced with "schedules"

:white_check_mark: thought for 51.4 seconds

Short answer: yes — in Prefect 3.x the field is `schedules` (plural). The old `schedule` (singular) was used in 2.x. If you’re seeing `schedule` in a 3.x context, that doc is outdated.

Authoritative docs:
- <https://docs-3.prefect.io/v3/how-to-guides/deployments/prefect-yaml|prefect.yaml reference (3.x)>
- <https://docs-3.prefect.io/v3/how-to-guides/deployments/create-schedules|Creating schedules for deployments (3.x)>
- For comparison, 2.x used `schedule`: <https://docs-2.prefect.io/latest/concepts/schedules/|2.x schedules>

Minimal 3.x example:
```
deployments:
  - name: my-deployment
    entrypoint: flows/my_flow.py:flow
    work_pool: { name: my-pool }
    schedules:
      - cron: "0 12 * * *"
        timezone: "UTC"
        active: true
      # you can define more than one schedule
      - interval: "3600s"
        timezone: "UTC"
```

If you can share the exact page you’re looking at, I’ll get it corrected. I do so love chasing stale docs.

<@U08G7SSNRST> can you share the docs link you're looking at?

Better with a link: <https://docs.prefect.io/v3/how-to-guides/deployments/prefect-yaml>

they're both (`schedules` and `schedule`) valid, which is somewhat confusing

It's called legacy schedule in the code <https://github.com/PrefectHQ/prefect/blob/main/src/prefect/cli/deploy.py#L1703>

yes, there was a push to switch `schedule` to `schedules` but then we got feedback from users that `schedule` made a lot of sense so we kept both, there may be places in the code that suggest that switch we underwent in the past