Hi, has anyone had issues with prefect.yaml when your entrypoint defined as module path

directory.flow:main

? It used to work for prefect 2.16, but latest version does not seem to be accepting it. @Marvin maybe you can help me?

It seems that there might be a compatibility or configuration change in the latest Prefect version causing the issue with the entrypoint defined as

directory.flow:main

. Here are a few GitHub issues related to similar challenges: 1. Ability to create/update from_source() based deployment without flow dependencies installed 2. First class handling of dependencies from pyproject.toml after git_clone pull step 3. ModuleNotFoundError after installing a local package successfully These discussions suggest changes around how dependencies and entrypoints are managed in Prefect. Although none of these issues mention the exact problem you're facing, they involve module paths and entrypoint configurations, which could give some insight or lead to a solution. Potential next steps: 1. Make sure you have updated your flow definitions and dependencies according to the latest Prefect documentation. 2. Verify that your module path and entrypoint configurations are compatible with the current version of Prefect. 3. Look into any migration guides or release notes between the version 2.16 and the latest version to catch any breaking changes that have been introduced. For more direct support, consider opening a new issue if you don't find a suitable solution from the existing ones or Prefect's Slack community. Would you like help with anything specific or to get more details on certain aspects?

Nor sure it helps to be honest