@Marvin I have a prefect.yaml file. Under the deployment section I want to add a cron schedule. Can you give an example of a full prefect.yaml file with cron schedule under deployment section?

You can add a cron schedule to your

prefect.yaml

file under the

deployments

section. Here's an example based on the Prefect 2.x documentation:

yaml
deployments:
  schedules:
    - cron: "0 0 * * *"
      timezone: "America/Chicago"
      active: false
    - cron: "0 12 * * *"
      timezone: "America/New_York"
      active: true
    - cron: "0 18 * * *"
      timezone: "Europe/London"
      active: true

Each schedule has a

cron

expression, a

timezone

, and an

active

state. You can customize these according to your needs. For detailed information, you can refer to the Prefect 2.x scheduling documentation here: Prefect Scheduling.

I have tried that. It looks like this: @Marvin deployments: - name: test_deploy.testflow # name of deployment version: # version tags: [] description: entrypoint: flow.py:test_new_deploy_flow # where flow is located. Should align with folder, i.e. folder+entrypoint should point to the full path of the flow parameters: {} schedules: - cron: "0 0 * * *" timezone: "Europe/Copenhagen" But does not work

The example you shared is almost correct, but there might be a slight misunderstanding with the structure in relation to cron schedules. Here's how you can properly format your

prefect.yaml

file for Prefect 2.x with a cron schedule:

yaml
deployments:
  - name: test_deploy.testflow  # name of deployment
    version:  # version
    tags: []
    description: 
    entrypoint: flow.py:test_new_deploy_flow  # entry point for your flow
    parameters: {}
    schedule:
      cron: "0 0 * * *"
      timezone: "Europe/Copenhagen"

### Key Points: 1. schedule: Make sure it is a single object under each deployment rather than a list of schedules as inferred. Each deployment can have its own schedule setup directly like above. 2. timezone: Ensure that the timezone you are using is valid according to the IANA Time Zone Database. ### Troubleshooting: - Ensure the Prefect Scheduler is Active: Verify if your Prefect server's scheduler service is running. Sometimes, if it isn't running, scheduled flows won't trigger. - Check Prefect Server Logs: Look at the logs for any errors that could point to why the schedule isn't triggering. For more detailed scheduling options, see the Prefect Scheduling Documentation. Try this format and let me know if it resolves the issue!

@Marvin when I use your suggestion it says that "schedule" is deprecetated and I should use "schedules" instead

Thank you for pointing that out. Based on the Prefect 2.x documentation, it appears that using the

schedules

section is indeed the correct way. Here's how your

prefect.yaml

should be structured:

yaml
deployments:
  - name: test_deploy.testflow  # name of deployment
    version:  # version
    tags: []
    description:
    entrypoint: flow.py:test_new_deploy_flow  # where flow is located
    parameters: {}
    schedules:
      - cron: "0 0 * * *"
        timezone: "Europe/Copenhagen"

### Explanation: - schedules: Make sure this is a list, even if you have only one schedule. This aligns with the current expected structure in Prefect 2.x. - cron and timezone: Keep them under each schedule in the list. This format should be properly recognized by the Prefect infrastructure. If there's still an issue, consider checking the Prefect version compatibility or any recent changes in scheduling features. For further detailed configuration, you can refer to the Prefect documentation on scheduling.

@Marvin how is that any different from how my code looks now

Your current configuration and my suggestion should indeed be quite similar if you've structured it as a list under

schedules

. However, I noticed that in your configuration the timezone key might not be properly indented under the cron schedule. Make sure the format is as follows:

yaml
deployments:
  - name: test_deploy.testflow  # name of deployment
    version:  # version
    tags: []
    description:
    entrypoint: flow.py:test_new_deploy_flow  # where flow is located
    parameters: {}
    schedules:
      - cron: "0 0 * * *"
        timezone: "Europe/Copenhagen"  # Correct indentation

### Potential Issues: 1. Indentation: YAML is sensitive to spaces and indentation. Ensure that

timezone

is correctly aligned under

cron

. 2. Active Field in Schedules: You might need to ensure that your schedule is active. Consider adding

active: true

under your schedule if that's supported and necessary. 3. Scheduler Running: Verify that your Prefect server's scheduler is active and configured properly if the scheduled jobs are not being executed. If you still encounter issues, please ensure you are using the correct Prefect version and that there are no typos. If all settings and formats are correct, then there might be an internal issue, which could require further investigation against Prefect logs or community forums.