Currently having issues with flows hanging when calling `get

Question

Currently having issues with flows hanging when calling `get run context ` from within a flow MRE in thread

Joshua Grant · Answer

```from prefect import flow task get run logger from prefect context import get run context task def print task obj logger = get run logger <http logger info|logger info> obj flow def test flow ctx = get run context print task ctx if name == main test flow ```

Joshua Grant · Answer

output is ``` gt python sample flow py 13 46 36 385 | INFO | prefect engine Created flow run thankful seagull for flow test flow ``` This will not finish until Ctrl+C

Zanie · Answer

This looks specifically like a bug in passing the run context from a flow to a task not calling `get run context`

Zanie · Answer

The flow run context is full of states and task run tracking information we re probably stuck doing resolution of states to data nested in the object

Zanie · Answer

If you just pass the data you need you should be fine I ll work on a fix for this though

Zanie · Answer

Note this definitely will not be supported if you re using a remote runner like Dask Why do you want to pass the flow run context to a task

Joshua Grant · Answer

We re currently migrating from 0 15 9 to 2 6 9 and have external tools that we send flow run information to

Zanie · Answer

What information do you need

Joshua Grant · Answer

currently we send flow id and run time flow id is used in some calls and we have a flow killer that kills a flow if it has run over 1 hr

Joshua Grant · Answer

There s probably a much easier way to do this now

Joshua Grant · Answer

I mean our external tool will have to be rewritten anyway as it highly utilizes GraphQL

Joshua Grant · Answer

instead of passing the entire context I got the `flow id` by passing `ctx flow run flow id` to the log statement ```14 30 49 797 | INFO | prefect engine Created flow run sepia hyena for flow test flow 14 30 49 873 | INFO | Flow run sepia hyena Created task run print task 3fb05284 0 for task print task 14 30 49 873 | INFO | Flow run sepia hyena Executing print task 3fb05284 0 immediately 14 30 49 890 | INFO | Task run print task 3fb05284 0 5c22623d 9c2e 4610 87c1 8fc6249938f7 14 30 49 900 | INFO | Task run print task 3fb05284 0 Finished in state Completed 14 30 49 910 | INFO | Flow run sepia hyena Finished in state Completed All states completed ``` Thanks < Zanie>

Zanie · Answer

+1

Zanie · Answer

< Marvin> open Passing the flow run context to a task causes deadlock

Zanie · Answer

Duno if the bot is good these days

Leon Kozlowski · Answer

Was this ever solved I m seeing similar behavior as well and wasn t able to find an issue on github

Joshua Grant · Answer

The way I solved it was to grab the information I need in the flow logic and pass that information along to tasks So in my flow I would have ``` flow def my flow ctx = get run context flow id = ctx flow run flow id my task results = my task flow id ```

Leon Kozlowski · Answer

Got it Thanks Joshua