Based on the information I found, here are some possible solutions:
1.
Work Pools: Make sure your work pools are properly configured. You can view and edit your work pools in the Prefect UI or via the Prefect CLI. More details can be found
here.
2.
Deployment Triggers: If you're using Prefect Cloud, deployments can take a trigger specification. This will configure an automation to run the deployment based on the presence or absence of events. More details can be found
here.
3.
Server Availability: Ensure that your Prefect server is not crashing or becoming unavailable. Flow runs need the server to be online. If your server went offline, it could explain why your pod never started. More details can be found in this
forum post.
If none of these solutions work, could you provide more details about your setup and the exact error message you're seeing?