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

I have a task that returns a connection integer:

`conn = await ccl_kdb_setup.grab_port_handle.submit(env, hmaster_port_number)`

But for some reason when I use it later, it's saying that it is a prefectfuture... This hasnt happend to me before, was wondering why that is the case espeically since i awaited?

The weird thing is if i did not have the print statement, it would run fine. BUT if i had the print statement, it says it's a prefect future.. how woud i be able to run the next task given that the conn variable should accept an integer and not a prefectfuture?

```    print("CONNECTION: " + str(conn))

    # Define the tasks with their dependencies, ensuring only tasks between start and stop are executed
    if "1_data_wait_initial_cache_posted_77" in tasks_to_run:
        task_functions[
            "1_data_wait_initial_cache_posted_77"
        ] = await ccl_kdb.async_query_access.with_options(
            tags=["data", "dataloader"], name="1_data_wait_initial_cache_posted_77"
        ).submit(query=".wf.wait[`INITIAL_CACHE_POSTED_77;6f;1f;120f]", conn=conn)```