https://prefect.io logo
Title
j

Joshua Fink

11/17/2022, 11:15 PM
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?
k

Kalise Richmond

11/18/2022, 5:07 PM
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?
j

Joshua Fink

11/18/2022, 6:04 PM
I'm super new to Prefect and the software space generally so could be making dumb mistakes...
Here is the test flow/deployment I made
Since it is a small test flow, figured I could try automatically scheduling deployments
I then start a prefect agent to run the work queue
First though i connect to my cloud workspace, then start agent
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
Here's how it appears on Prefect Cloud now
Thanks in advance. Lmk if I can send you anything else that would be helpful
k

Kalise Richmond

11/18/2022, 7:50 PM
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
j

Joshua Fink

11/18/2022, 8:13 PM
Wonderful thanks. Here's what I get when I run prefect version
This is in Powershell so maybe that could be the issue as well
Hi @Kalise Richmond any updates?
Thanks for all your help so far
k

Kalise Richmond

11/21/2022, 6:38 PM
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?