Anyone able to assist me on this after I updated to 2 7 6 al

Question

Anyone able to assist me on this after I updated to 2 7 6 all my scheduled flow is not able to run by the local agent they will show as Pending forever I ve posted my issue here as well <https discourse prefect io t prefect 2 7 5 2 7 6 flow stuck at pending forever 2149>

Zanie · Answer

Hi Previously you said that you were using a hosted API but your logs there show a client running with an ephemeral API talking to a database in your home directory

Zanie · Answer

Are the flow runs communicating with the same API database as your agent

Tuoyi Zhao · Answer

Hi < Zanie> i didn t aware of this What s the difference between the hosted and ephemeral API I connected to the one established by `prefect orion start` which should be that hosted locally

Zanie · Answer

In this image you can see it is using the ephemeral application rather than API at

Zanie · Answer

Is the `PREFECT API URL` set

Tuoyi Zhao · Answer

doesn t seem so what should I do now

Zanie · Answer

You ll want to set the API URL to your API looks like 127

Zanie · Answer

Then your flow run should contact the correct API and report its state

Tuoyi Zhao · Answer

< Zanie> I changed it to 127 0 0 1 4200 api However my scheduled flow run is still showing Pending state and agent shows frozen runpy

Zanie · Answer

Interesting

Zanie · Answer

The runpy warning is safe to ignore

Zanie · Answer

You see that running command text

Zanie · Answer

What happens if you go to the directory that it says there and run the prefect engine command it displays

Tuoyi Zhao · Answer

let me try that command directly

Tuoyi Zhao · Answer

< Zanie>

Zanie · Answer

mm you ll need to pass the flow run id to it just as the first argument

Tuoyi Zhao · Answer

like `python m prefect engine 9bcee788 6e55 4c99 8e86 cce0c66a58d8`

Zanie · Answer

yep

Tuoyi Zhao · Answer

< Zanie> It hangs in this state

Zanie · Answer

slightly smiling face Wonderful That s roughly what I expected but it s good to be sure

Zanie · Answer

We re stuck somewhere in this function <https github com PrefectHQ prefect blob main src prefect engine py L250>

Zanie · Answer

Probably retrieving your flow from storage

Tuoyi Zhao · Answer

great that we have a clue here slightly smiling face any idea how can i fix that

Zanie · Answer

Here s a branch with more logs

Zanie · Answer

`pip install git+<https github com PrefectHQ prefect log load>` then run that engine command again

Zanie · Answer

You can see the diff at <https github com PrefectHQ prefect pull 8075 files> if you want

Tuoyi Zhao · Answer

Here s the result btw I stopped the previous prefect orion and prefect agent before pip install

Tuoyi Zhao · Answer

wait after i initiate a new orion api by `prefect orion start` and execute that `python m prefect engine 9bcee788 6e55 4c99 8e86 cce0c66a58d8` now it shows the similar log as before

Tuoyi Zhao · Answer

basically stuck at connecting to API at | DEBUG | prefect client Connecting to API at <http 127 0 0 1 4200 api >

Zanie · Answer

Ah but it s stuck there on the downloading from storage

Zanie · Answer

And the storage path there is K A whole disk

Tuoyi Zhao · Answer

that s not good face with head bandage how comes my code actually stored in that K drive

Zanie · Answer

Is your code in some subdirectory directory of that drive This might be a problem with how the deployment is defined or created

Tuoyi Zhao · Answer

yes

Zanie · Answer

Are the contents of K being copied to the temporary directory where the flow is trying to run

Tuoyi Zhao · Answer

this is how the flow is built i built it right from the python code

Zanie · Answer

cc < Peyton Runyan> can you hop in here

Zanie · Answer

Can you share the output of `prefect deployment inspect` for that deployment

Zanie · Answer

It looks like we set the path to the directory you run the code from <https github com PrefectHQ prefect blob main src prefect deployments py L720>

Zanie · Answer

Can you create your deployment again but call `python` from the directory your flow is in

Tuoyi Zhao · Answer

i see let me try run the deployment code from the detailed drive path

Zanie · Answer

Do you know if you ran it from `K ` before

Tuoyi Zhao · Answer

< Zanie> It s working Thank you sooooooo much

Zanie · Answer

Np We ll look into some safeguards for this

Tuoyi Zhao · Answer

It s my bad not checking the working directory before running the script VS Code used to use the directory where the code resides slightly frowning face