Never mind Andrea, looking more carefully I noticed that after adding the optional=false to the first entity that was raising the problem, it actually failed for a different entity.
We have way too many entities to apply the optional=false, so I prefer to wait for the fix to be released, but I’m very confident it will work