The bug I’m looking at seems to be the result of using a configured cache before it has been resolved at all?