Ok, it's clear now that on the offending relationships, if I use includePaths and specify the fields, the problem doesn't occur. If I ommit this, I get the error most of the time but not always. It should be in initialization phase somewhere when indexedembedded fields are being analyzed. My assumption why this happens to me "most of the time" is that the order in which analysis occurs is not predetermined and that this order influences the outcome