this makes sense - but it is not at all clear in the UI. Thanks for the clarification.
I had this exact problem! Couldnât see delves just green check marks. I can confirm as well that disabling addons and reloading then turning back on resolves this problem.
Blizzard needs another 12 hours of maintenance to get it right.
No, this is an addon issue. The addons are or were assuming the Great Vault format would be the same as the last 2 expansions. Thatâs not Blizzard doing this in this context. I would guess the authors didnât have a way to test it in PTR hence the issues we are seeing now.
Fortunately, turning off Astral Keys did also solve the problem for me.
Its weird, some of my toons it shows World and others it shows PVP.
Edit: Turning off Astral Keys addon fixed the issue.
It also worked for me. Tyvm for the solutions. Best of luck on your vaults 
I have three addons which reference Blizzard_WeeklyRewards, but all three only call the interface on login. I think the issue is a combination of addon and Blizzard, because what seems to be happening is the addons are calling the Vault interface before it has fully initialized in the game and so we are getting legacy panes instead of the updated ones.
Blizzard could resolve this entirely by removing all the legacy panes for the Vault from the LUA code. Addons can resolve it by waiting 5-10 seconds before calling the function.
The three addons which reference it for me, for anyone who may have something besides AstralKeys and still sees the problem:
- AstralKeys
- SavedInstances
- Great Vault (which simply put a button on your minimap to open the window; easy to get rid of since you can click it on the Dornogal map now)
I also have GreatVault addon, turning it off fixed the vault display for me. Reenabling brings back the busted screen.
Disabling the addon Angry Assignments ( I donât have AstralKeys or GreatVault addon) fixed it for me.
Noting the âdisable list > re-enable listâ worked for me as well. Simply disabling Astral Keys did not alone fix this for me.
Blizzard isnât causing this issue, it is the addon authors. Donât get me wrong, Blizzard makes a lot of mistakes, but this is not one of them. I think youâll see my post history has been fairly even-handed. I will critique the hell out of them when they do something wrong. Equally, pinning the blame on them because theyâre an easy target on something they didnât do is not what I will do.
Addon authors did this as a matter of expediency. Blizzard could rewrite their backend to resolve a problem that isnât caused by them, but no development team would do that unless the bug in question was either against the ToS or breaking normal functionality (i.e. you canât move your character or interact with the UI). Thatâs not the case here. Nor would they prioritize it either.
Workaround is available and working: Disable the offending addons. Addon authors either need to update their addons or admit they donât intend to do so (i.e. people stop using them anyway). In the end, not a Blizzard problem nor a Blizzard required solution.
Blizzard left legacy, obsolete assets in the game files which are still being used if a race condition is met. There is absolutely something they could do, as there is no reason to keep those legacy assets in the interface code any longer.
As I said, the only change any of these authors can do (the three I listed, at least) is add a delay before they call the function. They are all simply calling a function supported by the game which loads the interface frame invisibly in order to get its data. None of them are actually touching the frames inside that window in any way.
Again, my main point is that there are solutions at both ends. Not all things are absolutes, and I didnât place direct blame at only Blizzardâs feet.
Blizzard leaves legacy assets in the interface code for literally every expansion. Youâre drawing a very interesting line on where you think they should behave. Thatâs not consistent with their last 20 years of work.
Itâs very clear your agenda here, but letâs be clear, itâs not standard practice for them or most games with multiple expansions behind it. What youâve suggested is not inline with their behavior and it isnât necessary here either. Addon authors have the smallest amount of work to do here and they are the origin of the problem - not Blizzard.
If I had my druthers? Iâd have them remove addons altogether and be done with this entitlement by people who donât develop addons.
Itâs pretty clear to anyone reading the thread and these responses that you are the one with the agenda. Iâm not going to engage with this further. Have a good life.