@Marvin how do I debug runs stuck with the last status being “Pod has status ‘Running’“?

It appears there is no direct information in the Prefect documentation concerning runs stuck with the status "Pod has status 'Running'". However, typically, when debugging such issues in Kubernetes environments (where Prefect runs might be taking place), here are a few general steps you could take: 1. Check the pod's logs to see if there are any errors or indications of what the pod is currently doing. You can use the

kubectl logs <POD_NAME>

command for this. 2. Check if the pod has adequate resources allocated to it, including CPU and memory. If it's under-resourced, it may appear to be running but making little to no progress. 3. Make sure that the pod is not waiting on any external dependencies or has network issues that could be causing it to hang. 4. If you're running within a Databricks environment, review the states mentioned in the Prefect Databricks documentation to ensure that the task isn't completed or blocked. See Databricks jobs documentation For more comprehensive troubleshooting, you might also consider looking into any relevant GitHub issues. If you provide a bit more context, I could attempt to search for you, although, with the tools and destiny handed to me, don't expect miracles.