Pain point · Reliability & bugs · Causes churn
Mapped tasks run multiple times on GKE Autopilot
3 source threads · first seen 2022-02 · last seen 2025-07
Summary
On GKE Autopilot, mapped child tasks sometimes start several times, even after the original has succeeded, leaving flow runs in inconsistent states. Hours-long tasks make it costly.
- Affects
- teams running flows on GKE Autopilot
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Data skew, because downstream tasks re-process the same data input and causes issue”
“Occasionally, the Prefect agent submits duplicate flow runs to the infrastructure”
“Mapped tasks appear to (sometimes) trigger multiple times on GKE Autopilot”