Björn Heiß

Note to my future-self. The error states the quest that is missing is: https://www.wowhead.com/classic/quest=825/from-the-wreckage While the user reports it happened on turn in of https://www.wowhead.com/classic/quest=813/finding-the-antidote

@Hardstyler21127 @anon1231823 @SaintKatherine @Nerillida @Balu-bln Were you using the RestedXP addon and/or Leatrix Plus when the error above happened (you reported a very similar in the past)

Some notes, to maybe figure out similarities 1. #5067 shows that the error happened when `QuestLogCache.GetQuestObjectives` was called through `Questie:SendMessage("QC_ID_BROADCAST_QUEST_UPDATE", questId)` inside `QuestieQuest:AcceptQuest` 2. #4842 shows that the error happened...

0d57edf3920d11b0efacb2df23e21798a4a42275 is a first step to counter this.

Copying the content of https://github.com/Questie/Questie/issues/6864#issuecomment-2623925289: > A few notes from the chat (Thanks again @SirWeinalot ): > > - All three quests that error are not tracked > - All...

I noticed that `QuestLogCache.CheckForChanges` can be called for quests which simply never return correct objective data, thanks to the Blizzard API. With the release of the MoP pre-patch multiple reports...

Another case of this bug happened (see [Discord link](https://discord.com/channels/263036731165638656/579966856085897216/1395769993836101643)). An interesting detail is, that the user did these two quests on two different characters and got this error on both:...

The current idea about what is causing it, is that the usage of `TaskQueue:Queue` (initially only used in `QuestieQuest.AcceptQuest`) brings in async problems in the event order. The TaskQueue processes...

Ah yeah, we definitely need to further improve these hints for things outside of SoD. Thanks for reporting this @reconisance

Yep, same here.