Is it possible to use the imperative API to have child tasks that live in multiple files? Ex: File 1 makes a flow that calls a task in File 2. This works so long as the task in File 2 doesn't call another task within File 2. If I try to do that, I get a

ValueError: Could not infer an active Flow context.

Hi Kyle - I don’t think this is related to file structure at all; tasks shouldn’t be calling other tasks. The Flow is the container that is responsible for stringing other tasks together.

@task
def task_one():
    pass

@task
def task_two():
    task_one() # will raise an error, always

I see. My end goal is to take a list of files, map them, and have tasks for extract, transform, load, etc. In my current setup, I take the list of files and call a process() task that was trying to call subtasks for ETL

you can keep calling

.map

successively to create longer mapped pipelines, e.g.,

with Flow("my-mapped-flow") as flow:
    task_three.map(task_two.map(task_one))

I'll give that a shot later. Thanks!

👍 👍

@Chris White and in this nested map, should a task fail somewhere in the middle, will it terminate that branch?

yea all tasks downstream of the single mapped task will enter a

TriggerFailed

state, but other branches of the map will continue uninterrupted