<@ULVA73B9P> a colleague is running flows develope...
# ask-marvin
g
@Marvin a colleague is running flows developed under python 3.10.12 in prefect 2.14.16 locally with prefect version >= 3. The flow can run, but in the UI the status for the deployment is shown as not ready and the parameters defined for the flow are not displayed. Why?
m
It seems like the issue your colleague is facing with the Prefect UI showing the deployment status as "not ready" and parameters not being displayed could be related to a few known issues and configurations in Prefect 3.x. 1. Deployment Status "Not Ready": The status of a deployment can be influenced by the polling status of work queues. A work queue is marked as "NOT_READY" if a worker hasn't polled it in the last 60 seconds. Ensure that the workers are actively polling the queue associated with the deployment. More details can be found in the Prefect documentation on work pools. 2. Parameters Not Displayed: There is a known issue where rerunning flows with the same idempotency key does not register correctly in the UI, which could potentially affect the display of parameters. This issue is documented in GitHub Issue #9483. To address these issues, ensure that the work queues are properly configured and actively polled by the workers. Additionally, consider checking the idempotency keys used in deployments to see if they might be affecting the UI's display of parameters. If the issue persists, you might want to follow up on the GitHub issue for any updates or workarounds.
g
@Marvin would need a work queque be started for verything to be displayed properly?
m
Yes, for the deployment status to be displayed as "READY" and for everything to function properly in the Prefect UI, a work queue needs to be actively polled by a worker. If no worker is polling the queue, the status will remain "NOT_READY", which can lead to issues with the display and execution of deployments. To resolve this, ensure that: 1. A worker is started and is polling the appropriate work queue. 2. The work queue is configured correctly to match the deployment requirements. This setup should help in getting the deployment status and other related UI elements to display correctly. If you need more detailed instructions on setting up work queues and workers, you can refer to the Prefect documentation on work pools.