👋 I don't understand what changed in Prefect 2.0 cloud / agents recently. Everything was running smoothly but now when I start my agent, As soon as I strat a quick flow run, the work pool becomes unhealthy and I get the following error sometimes (most of the times I don't get any error).

does not have an infrastructure pid attached. Cancellation cannot be guaranteed.

It's very hard to have more logs than that so it's hard to understand the problem and debug. Any help would be helpful 🙏 Some more context • The agent is deployed in GCP VM • I use the exact same command line than specified in Cloud • Stopped working last week with Prefect 2.7.* on the agent side. Same problem with 2.10.*

@Matt Delacour Maybe I'm wrong here, but aren't work pools feature still in beta?

Maybe it's misleading but I used to spin up agents and doing the exact same command does not work anymore ... And today my agent cannot pull any jobs as it uses to be

I’m starting to see a lot of similar behavior with an agent going down every few hours. I’m going to get my traceback and share as well

Thanks @Nelson Griffiths Happy to collaborate on that. Hopefully someone from Prefect will also look at it 🙏

@Matt Delacour I came across this and it seems to have fixed my issues https://github.com/PrefectHQ/prefect/issues/7442

Thanks for sharing

@Matt Delacour I’m experiencing the same issues. I’m running my agent on ECS Fargate and my agent has become unreliable ever since prefect v2.10

Please add your comment in the issue mentioned above https://github.com/PrefectHQ/prefect/issues/7442 For some people people having the following ENV var set up fixes it

PREFECT_API_ENABLE_HTTP2=false prefect agent start

ill try that env variable and see what it does. ill comment on that PR too