Does anyone know why my scheduler is not picking up my schedules properly? I have 2 schedules on a deployment, weekday runs and weekend runs. Both have been enabled since the beginning of the week, and the weekday one has properly triggered some flows. However, it seems like the scheduler is not reliably scheduling the weekday runs, it only picks up the weekend ones (see screenshot from this morning). Is there a configuration that I'm missing to get this to properly pick up both?

Hey Tom! Can you DM me the url to your deployment? Will let me share it with the right folks internally to get 👀 on it

Hey Adam, unfortunately it's a self hosted instance

no worries! the math to an MRE is going to be marginally longer, but no sweat

Cool, thank you! Happy to provide any additional details from the setup to help get this fixed

yep! the thing that would help the most is if you wanted to share a quick hello_world flow with the the specific schedules you used. happy to take it off your plate either way

prefect --version =

2.17.1

`prefect.yaml`:

...
- name: hello-world
  entrypoint: flows/hello-world.py:execute_hello_world
  work_pool: *common_work_pool
  schedules:
    - cron: '30 9,13,16,23 * * 1-5'
      timezone: America/Los_Angeles
      active: true
    - cron: '0 11 * * 0,6'
      timezone: America/Los_Angeles
      active: true
  build:
    - prefect_docker.deployments.steps.build_docker_image:
        <<: *docker_build_config
        image_name: '{{ $CONTAINER_REGISTRY }}/internal-dwh-hello-world'
...

hello-world.py

:

from prefect import flow

@flow
def execute_hello_world():
    print(f"Hey")

if __name__ == "__main__":
    execute_hello_world()

🙌

Thank you! Fwiw, I'm NY too but my org is mostly west coast, don't hold that against me haha

Yeah something about a los angelino working before noon felt off

Also one other thing, in the deployment, they were as active=false, and I manually turned them on in the UI. Not sure if that would have any impact here

oh yep that feels super relevant

Thanks Adam, I tried a redeploy with the schedules enabled in the yaml and am still seeing the issue. It seems like what's happening is the scheduler tries to deploy 3 of the weekend schedules and then doesn't try on the weekday schedule any more. I think the multi-schedules doesn't seem to work properly on this version as its happening on several pipelines that are configured this way