I have a workspace where FeatureMerger_2 and 1/3 connection is disabled, but when I trigger a Partial Run from the upstream reader BODENBEDECKUNG_A, I get the "Caches required to run translation are missing or stale" prompt, listing all the transformers that feed into that disabled FeatureMerger (See attached screenshot)
Since the FeatureMerger itself won't execute, I'd expect its exclusive upstream feeders to be treated as dead and excluded from the run, but apparently they are still required
If I instead disable each incoming connection to the FeatureMerger, the feeders correctly drop out of the run and I don't get the prompt, even when Feature Merger is enabled.
Can someone explain the logic here? Why does disabling a transformer and the relevant connections (the one coming from the reader where the Translation is started) not back-propagate to exclude its upstream feeders, while disabling the connections does?


