Hi @scotbaston,
I’ve been looking at this and I really wish I had a near term solution to offer here. Unfortunately, the only thing I can suggest right now is moving the Looper Providers into the Global Blocks.
The problem is that I didn’t anticipate loopers being used like this, and so while it may have worked somehow for a time, it wasn’t actually meant to… What should actually be happening here is Global Blocks (and Content Builder items when called inside the Layout Builder) should begin a fresh context and have no awareness of the parent. That’s closer to what is happening now, but there is still some state management going awry and it’s not fully cleaned up (you can still get to some Dynamic Content items).
I’m sorry, I’m sure this isn’t the news you were hoping for. I’ve been looking at it for a bit now and I don’t have a safe way to get the former “functionality” back without breaking something else, and I would actually prefer long term to not support a Looper Provider and Consumer relationship to break the boundary being in separate builder content.
What we really need here is Global Elements that keep their content and styling, but can be fully managed directly inside the builder you’re in rather than being managed in a separate builder. This is something we’ll be exploring after responsive styling is complete.