@Marvin My deployments keep showing "This deployment has not been polled in the past 60 seconds" ? Is there any config that needs to be changed for this to be resolved ?

It seems like your issue could be related to a Prefect deployment's status not being updated or expired deployments. Prefect has introduced a component called Foreman that handles the status of deployments, including timing out deployments that haven't been recently polled. It might be possible that in your case, the polling mechanism hasn't updated the status due to a misconfiguration or an issue in the Prefect deployment or worker setup. Here are some steps and considerations to resolve the "deployment not been polled" issue: 1. Check the configuration of your Prefect deployment to ensure it is set to poll for updates correctly. 2. Ensure that your work pool is configured correctly, and there's a worker that pulls work from the correct work pool. If you're using a pull-based work pool, you need an external worker that is active and polling for work. 3. Verify that your infrastructure (e.g., Docker, Kubernetes, etc.) is running properly and that there are no network or permission issues that might prevent workers from polling the Prefect API. 4. The issue might be related to deployment setup, in which case, reviewing your deployment definition and infrastructure setup might help to identify any potential problems. 5. Consider reviewing recent changes to Prefect that might affect deployment polling, in case an update has introduced a new behavior that affects your setup. If these general pointers don't solve the problem, it might be helpful to look into the specific logs and configurations of your system. You may also want to reach out to Prefect's support or community for assistance, as they can provide more targeted help. For more information, you can review the Prefect documentation on deployments and check if there are any specific configurations you might be missing. If you are experiencing a persistent issue, you may want to search through open Prefect GitHub issues or create a new issue detailing your problem for support from the Prefect development team. Here are some related issues from GitHub that you might find informative: - Deployment status persistence and events - Unnecessary scrollbar in deployment overview - Deployment name with slashes get truncated - Intermittent fatal error running deployment with docker infra - Changes in the logic of the deploying work pools Keep in mind that this is a starting point, and you may need to adapt the suggestions to fit the specifics of your infrastructure and Prefect setup.

hi @Abhishek Singh - do you have a worker that is running and healthy?

yep it kept showing as healthy I have since changed the prefect db from sqllite to pgsql and it has sorted it as i was getting multiple blockings when prefect was trying to write stuff in its sqlite db