Same problem here with my graph having a double-nested map-reduce pattern, where A -> Send([B, C]) and B -> Send([D, E]) with C -> A and D -> A and E -> A

The problem manifests as:

• Node A doesn't wait for all edges (D, E, and C) to complete before starting

• A can be triggered with only C completed, then again with D and E

• This violates the expected map-reduce behavior where the reduce phase should collect all results before proceeding

I tried also to set the parameter defer=True for the A node as advised in the doc, but still have the same issue.