@Marvin I have a task that is being executed with .map. And the result of this task is being passed to a subflow. This task is being executed 2 times and the subflow just execute one time. I need that the subflow for each task.

In Prefect, when using

.map

to execute tasks, each task execution typically corresponds to a separate invocation of the function or subflow it's mapped to. If you're finding that your subflow is only executing once instead of once per task execution, it might be due to how the subflow is being invoked or structured. Here are some points to consider: 1. Ensure Subflow is Mapped: Make sure that the subflow itself is being called within the mapped task. This means that the subflow should be part of the task's execution logic that is being mapped. 2. Check for Conditional Execution: Verify that there are no conditions or logic that might be preventing the subflow from executing for each task. 3. Use of

.submit()

: If you're using async tasks or subflows, ensure that you're using

.submit()

to properly schedule each execution. This is particularly important if you're mixing synchronous and asynchronous tasks. 4. Review Execution Context: Ensure that the execution context for each task is correctly set up to invoke the subflow. This can sometimes be a problem if the subflow relies on shared state or resources that aren't correctly initialized for each task. Here's a basic pattern for how you might structure this:

python
from prefect import flow, task

@task
def process_item(item):
    # Some processing logic
    return item

@flow
def subflow(item):
    # Logic for the subflow
    print(f"Processing subflow for item: {item}")

@flow
def main_flow(items):
    results = process_item.map(items)
    for result in results:
        subflow(result)

items = [1, 2, 3]
main_flow(items)

In this pattern, each item is processed by

process_item

, and then the

subflow

is called for each result. Make sure your actual implementation aligns with this structure if you want each task to trigger its own subflow execution. For more details on task mapping and subflow execution, you might want to explore Prefect's flow and task documentation.