Hello We re trying to migrate from Prefect 1 to 2 but we wan

Question

Hello We re trying to migrate from Prefect 1 to 2 but we want to run both concurrently on the same data to verify the output is the same Both lib versions can t be installed at once so I m using the REST API to trigger jobs We have a flow set up that works and that we ve tested launching through the UI I ve followed and my code looks something like this ``` data = parameters params flow id cfd9e6db deployment id 24583f30 4 infrastructure document id 0181dc52 tried without the next key entirely and in PENDING state type RUNNING r = PREFECT2 URL json=data headers= Authorization f Bearer api key ``` The flow is created but it doesn t pick up the work queue properly and so it just stays in the state but nothing happens See below the green run was triggered in the UI the other two were sent in as SCHEDULED and RUNNING respectively Any suggestions on getting this to run would be much appreciated Thanks

Shayne Hodge · Answer

Here s an example response ``` id 585e9cad created 2023 01 12T21 03 29 623120+00 00 updated 2023 01 12T21 03 29 625422+00 00 name modest ladybug flow id cfd9e6db state id 1e0299c4 deployment id 24583f30 work queue name None flow version None parameters documentset id 08eff4a9 idempotency key None context empirical policy max retries 0 retry delay seconds 0 0 retries None retry delay None pause keys resuming False tags parent task run id None state type RUNNING state name Running run count 1 expected start time 2023 01 12T21 03 29 622674+00 00 next scheduled start time None start time 2023 01 12T21 03 29 622674+00 00 end time None total run time 0 0 estimated run time 0 053743 estimated start time delta 0 0 auto scheduled False infrastructure document id 0181dc52 infrastructure pid None created by id 48387560 type USER display value shaynetomecom work pool name None work pool queue name None state id 1e0299c4 545e 4939 b75e 7b1a88fdf182 type RUNNING name Running timestamp 2023 01 12T21 03 29 622674+00 00 message None data None state details flow run id 585e9cad task run id None child flow run id None scheduled time None cache key None cache expiration None untrackable result False pause timeout None pause reschedule False pause key None ```

Mason Menges · Answer

Hey < Shayne Hodge> Do you have the agent logs for these flow runs are they just running locally through the deployment generally speaking if the flows are getting stuck it indicates and issue in the execution environment

Shayne Hodge · Answer

So using prefect cloud with agents in ECS Agent logs show absolutely nothing it doesn t appear anything is reaching them If I kick it off from the UI logs appear

Shayne Hodge · Answer

The consistent difference between runs from the REST API vs from the UI is the API ones have no work queue attached

Nimesh Kumar · Answer

Hi shayne I am also trying to trigger my flow from outside using api post request can you share this code and the PREFECT2 URL you have used here Thanks