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.