Our optimisations in support of faster invokers and listeners (, ) have been too aggressive. We adopted a simple check at the site of a reference, whether the site itself had constructed, in order to determine whether to use the "fast route" or "slow route" for context resolution. This fails in the case where a child component has the state "constructed" but its parent does not, and the parent has further children whose contexts are only accessible via the "ginger member rule" that is our sole concession to component-level gingerness prior to FLUID-4925.

from fluid.expander.fetch:

In order to avoid degrading performance here, we will have to introduce a new lifecycleStatus which will be propagated by flooding to children once a parent is constructed.