@Marvin We upgraded our prefect server to version 3.2.5 yesterday. Today I noticed that all of my scheduled flows were triggered twice

It seems you're not alone in experiencing issues with scheduled flows being triggered multiple times. This problem has been reported by other users in the Prefect community, as seen in this GitHub issue. Although the specific issue you are encountering wasn't directly addressed in the latest release notes for Prefect 3.2.5, you might want to monitor the issue tracker for updates or workarounds. Here is the link to the release notes for reference. If this is causing significant disruption, consider reaching out to the Prefect community or support for more immediate assistance. In the meantime, you might want to double-check your flow configurations and schedules to ensure there aren't any unintended duplications.

@Marvin which recipe is used when we deploy our files to S3? ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/docker-azure/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/docker-s3/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/docker-git/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/azure/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/git/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/local/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/gcs/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/docker/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/docker-gcs/prefect.yaml ./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/s3/prefect.yaml

When deploying your files to S3, the appropriate recipe to use is located at:

./usr/local/lib/python3.12/site-packages/prefect/deployments/recipes/s3/prefect.yaml

This file should contain the configuration necessary for deploying to Amazon S3.

@Marvin if I update the schedule of a flow directly on the prefect server ui. Where is this change stored? Is it in a file on the prefect server or is it on the database?

When you update the schedule of a flow directly in the Prefect Server UI, the change is stored in the Prefect database, not in a file on the server. This allows Prefect to dynamically manage and execute schedules without relying on static configuration files. For more details on scheduling in Prefect, you can refer to the documentation on adding schedules.

@Marvin if I update a schedule through the prefect.yaml file and I deploy that, where is the schedule saved?

When you update a schedule through the

prefect.yaml

file and deploy it, the schedule information is stored in the Prefect database. This ensures that the Prefect server can manage and execute the flow runs according to the new schedule. The

prefect.yaml

file itself serves as a source of truth for deployment configuration, but the actual schedule execution is handled by the Prefect infrastructure.