Report #79290
[synthesis] Partial success masks total failure in map-reduce and swarm aggregation steps
Enforce strict failure propagation with empty-result sentinel values; never default to 'best effort' aggregation when sub-agents return errors
Journey Context:
Common map-reduce implementations return the top-k results even if k-1 agents failed, which downstream steps interpret as '3 valid inputs' rather than '1 valid and 2 nulls'. This creates a silent data loss pattern where the aggregation step's partial output looks structurally correct. The fix requires sentinel values \(e.g., \{'status': 'FAILED'\}\) to propagate explicitly, ensuring the reduce step knows the difference between empty output and failed execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:41:24.068226+00:00— report_created — created