Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi all, if I am trying to run a Flow run through a normal IDE debugger but keep seeing the value of Task outputs assigned to variables as &lt;Task:name&gt; types, am I returning the value of tasks wrongly or using the debugger wrong?

Hi <@UQ9FUDQKD>! That appears to be the repr of the task.  For example, in IPython:

```from prefect import Task

print(Task(name="Chris"))
# &lt;Task: Chris&gt;```

Hey! yep understood. I'm trying to do a normal debugger flow but I guess I'm unclear where the flow actually returns and assigns a Tasks output to the variable?

hmm I don’t think I’m following quite yet; would you mind sharing a code example of what you’re referring to?

```
with Flow("Mapbox API Travel Time Retrieval and Processing") as flow:

    download_geojson_blob_task = DownloadBlobFromAzure()

    azure_blob_name = "travel_time_segments.geojson"
    azure_container = "ottawa-mapbox-travel-time-inputs"

    travel_time_segments_geojson = download_geojson_blob_task(
        blob_name=azure_blob_name,
        azure_credentials_secret="AZ_CREDS",
        container=azure_container,
    )```


```...state = flow.run(executor=LocalExecutor())```


but not specific to instantiated tasks, functions with @task decorator are the same

that Flow code makes sense to me - does it not run as you expect?

it runs but I'd like to insert a break point but the variable I assign a task to is that type instead of the returned dict or what have you

so I clearly don't understand something about prefect

gotcha; where are you inserting your breakpoint?

so Prefect builds up a deferred computational graph, meaning your code is never run until you call `flow.run` - so inputting a breakpoint within the _build_ step of a Flow will not contain any results / data since nothing has run yet

should I step through then after the .run call

the data that is exchanged between tasks are always exchanged via Prefect States; when you call `flow.run` a Prefect State is returned whose `result` attribute is a dictionary mapping Tasks -&gt; task states, which have a `result` attribute themselves containing the return value from that task run

so using your code above, you could do:

```flow_state = flow.run()
flow_state.result[travel_time_segments_geojson].result```

to actually extract the return value of that task

<@ULVA73B9P> archive “How can I inspect the outputs from my tasks?”

<https://github.com/PrefectHQ/prefect/issues/1763>