Prefect Agent and and Orion both are up, yet the flow on cloud: 2.0 is scheduled only and paused in the late state

Looks like your agent is connected to api.prefect.cloud not to 127.0.0.1

Yeah I am working on cloud i.e api.prefect.cloud

“orion start” starts a separate backend. You would want one or another, but not both

No,

prefect orion start

is not required for Prefect Cloud. Cloud hosts an instance of the orion server for you.

Alright. So now what could be the reason for flow for getting into late state?

Your flow is likely “uploaded” to the “local API”, not the Cloud API. Having the agent connected to the Cloud API, the “local API” probably has no agents connected?

@Jenia Varavva okay but flow is there on cloud correct me if I am mistaken here

You’re right, I must be mistaken. I was referring to your first screenshot with 127.0.0.1. Will let orion experts answer this one

Trying to understand why a prefect flows on cloud:2.0 is getting in late state when agent is running on terminal.

Hey @Hafsa Junaid this one's kind of a long shot but do you have any tags specified on your deployed flow? If so you'll want to make sure the agent is started while specifying those tags as well.

No tags on deployed flow, but there is a tag with queue.. I have tested starting agent with both queue id and tag.. flow on cloud is still not starting @Mason Menges

Can you create a workqueue without any tags and try starting the agent with that queue?

@Mason Menges It worked, Thanks

No problem 😄