Hi does anyone know why Prefect Cloud leaves deployment inst

Question

Hi does anyone know why Prefect Cloud leaves deployment instances as Pending rather than Completed despite the fact that the Prefect Agent seems to have no issue completing the task itself Is this some sort of firewall issue

Kalise Richmond · Answer

Hey < Joshua Fink> that seems odd Are these flow runs or task runs Could you provide more details like a screenshot of what you re seeing or the Pending run id

Joshua Fink · Answer

I m super new to Prefect and the software space generally so could be making dumb mistakes

Joshua Fink · Answer

Here is the test flow deployment I made

Joshua Fink · Answer

Since it is a small test flow figured I could try automatically scheduling deployments

Joshua Fink · Answer

I then start a prefect agent to run the work queue

Joshua Fink · Answer

First though i connect to my cloud workspace then start agent

Joshua Fink · Answer

It appears to be submitting flow runs and completing when I run the agent locally on my machine The tasks are scheduled on Prefect Cloud and switch from Scheduled or Late to Pending when they are handled on my machine but it doesn t ever say Completed despite successfully being completed

Joshua Fink · Answer

Here s how it appears on Prefect Cloud now

Joshua Fink · Answer

Thanks in advance Lmk if I can send you anything else that would be helpful

Kalise Richmond · Answer

Thanks for providing all this detail I m going to test out locally and see if I can reproduce what you are seeing Just to make sure which version of Prefect are you using

Joshua Fink · Answer

Wonderful thanks Here s what I get when I run prefect version

Joshua Fink · Answer

This is in Powershell so maybe that could be the issue as well

Joshua Fink · Answer

Hi < Kalise Richmond> any updates

Joshua Fink · Answer

Thanks for all your help so far

Kalise Richmond · Answer

Hey < Joshua Fink> I m still looking into this So far what I ve seen locally and I m using Mac is that the agent is getting the submissions but then the agent goes into unhealthy which means it stops communicating with the api and therefore those flow runs are still in pending My theory is the administrator is blocking the creation of new processes Are you able to start the agent as admin administrator Have you enabled debugging `PREFECT LOGGING LEVEL = DEBUG ` and lastly are you submitting the flows with deployments through the CLI or the UI