@Marvin what could be causing this warning on deployment?:

conflicts with another flow. Consider specifying a unique `name` parameter in the flow definition:

 `@flow(name='my_unique_name', ...)`
  warnings.warn(

All the flows have unique names. It does re-register existing flows to deploy any changes, maybe that is the cause?

The warning you're seeing might be related to the way Prefect handles flow registration. In Prefect 2, flow pre-registration is no longer required. Instead, you create a Deployment that specifies the entry point to your flow code. If you're re-registering existing flows to deploy changes, this could potentially cause conflicts if the system still has a record of the old flow registration. If all your flows have unique names and you're still seeing this warning, it might be a good idea to check if there's any lingering metadata from previous flow registrations that could be causing the conflict. You might also want to ensure that your deployment process is correctly handling the new flow registration process in Prefect 2. For more detailed help, you might want to post this issue on the Prefect discourse.

@Marvin I am using Deployment.build_from_flow and then .apply()

Based on the issues I found, it seems that there are a few potential causes for the warning you're seeing: 1. There might be an issue with the way Prefect is handling the creation of a new database in the working directory. This was reported in this issue, where the user was using

Deployment.build_from_flow()

and

apply()

, similar to your case. 2. There could be a problem with how Prefect is handling flow runs in different work pools. In this issue, the user reported a warning when running a deployment with a pool name other than

default-agent-pool

. 3. There might be an issue with how Prefect is handling Kubernetes tolerations. In this issue, the user reported that attempting to patch in pod tolerations through either customizations or infra_overrides does not appear to work. 4. There could be an issue with how Prefect is handling the pausing of flow runs from the UI. In this issue, the user reported that pausing a flow run from the Prefect Server UI will exit the flow entirely instead of pausing it. 5. There might be an issue with Prefect not finding a custom block. In this issue, the user reported that Prefect 2.10.11 does not find a custom block, while Prefect 2.10.10 does. It's hard to say for sure without more information, but these issues might provide some insight into what's causing your warning. I would recommend checking these issues and see if any of the solutions or workarounds mentioned there help resolve your warning. If not, you might want to consider opening a new issue in the Prefect GitHub repository to get help from the Prefect team.