Beta tracking problems join the WoW Forever known issues
What Wowhead's World of Warcraft: Forever beta report says about Known Issues on Beta Updated, and what it leaves unconfirmed.
Editorial record
Responsible editor: Max · medium risk · automated review · AI assistance: draft
For players searching wow forever known issues, the update means several beta tracking and display systems should be treated as unreliable for now. Wowhead reports that Blizzard updated the list after a beta build update, with two fixes planned for the next beta build and several new issues recorded under September 24. Wowhead attributes the update to a Blizzard forum post.
What changed
The report says Sentinel Lynessa Duskblossom’s movement and repeated Strike use during 
Teldrassil’s “Escaping Ban’ethil” quest are due to be fixed in the next beta build. Loch Modan’s “Snowbound” quest is also due to receive an experience adjustment because its reward is higher than intended.
The newly listed problems affect several parts of the beta:
Bane and curse tracking can fail after a player drops and reacquires a target that already has one.- Healthstone,
Arcane Blast, pet, item-enhancement, and some other cooldown tracking does not work correctly. The report gives Windfury and rogue poisons as examples of affected enhancements. - Priest tracking defaults to all spells. Mana Gem tracking may not begin until the mage casts another spell.
- Changing or creating a party composition may move players to a different world instance.
- The Stormwind minimap has display problems, and Personal Resource Display does not show combo points.
What it means for beta players
Treat tracking readouts as beta limitations rather than dependable records while testing these systems. Party changes may also place players in another world instance. The report says improvements are in progress for that behavior, while the minimap issue is slated for a later build and another update is expected.
The evidence is limited to a Wowhead report observed from its published text. It does not provide a published Forever build number, exact dates for the next or later builds, a complete Known Issues list, or proof that every listed problem will be resolved before release.