Bug description

I updated to Questie version 7.4.12, and I logged into my character. I did not interact with the game world in any way during the Questie DB update. (I did not even move my character as I was looking at my phone.) The error message asks if I accepted a quest, but I did not.

[06:43:42 PM] Questie DB has updated! Data is being processed, this may take a few moments and cause some lag...
[06:43:42 PM] [1/9] Loading database...
[06:43:43 PM] Changed Channel: [5. kewlkidsclub]
[06:43:43 PM] Changed Channel: [6. rodanheals]
[06:43:43 PM] [2/9] Applying database corrections...
[06:43:43 PM] [3/9] Initializing townfolks...
[06:43:44 PM] [Questie] The 'Lunar Festival' world event is active!
[06:43:46 PM] [4/9] Initializing locale...
[06:43:46 PM] [5/9] Optimizing waypoints...
[06:43:47 PM] [6/9] Updating NPCs...
[06:43:55 PM] [7/9] Updating objects...
[06:43:58 PM] [8/9] Updating quests...
[06:44:01 PM] [9/9] Updating items...
[06:44:05 PM] Questie DB update complete!
[06:44:06 PM] Coxor has gone offline.
[06:44:08 PM] Questie: [ERROR] Did you accept a quest during InitQuestLog? Please report on Github or Discord. Game's quest log cache is not ok. This shouldn't happen. Questie may malfunction.

Screenshots

Questie & WoW version

My Questie version 7.4.12, and I am playing version 3.4.1 (Wrath Classic) of the game.

I should add that I did not receive a Lua error. BugSack showed everything was clean.

I will also add the Questie.lua variable file that is account wide in case it holds the quest log cache for inspection. I added .account.txt to the end for it to upload. (GitHub doesn't like Lua files)
Questie.lua.account.txt

Does it give the same error after a restart/relog?
If so, run this command in chat to rebuild the database again
/run Questie.db.global.dbIsCompiled = false;ReloadUI()

out of curiosity, are the game quest log cache and the questie DB linked?

out of curiosity, are the game quest log cache and the questie DB linked?

Usually a reload is enough when getting cache error, but if it happened during database build and the problem persists it might be worth doing that step again.

I am going to close this Issue because I am unable to replicate the error after running the provided command to manually rebuild the database. I now believe this is most likely to be user error on my part. Thanks!

It's not really user error, our code is just not prepared for every eventuality which can happen with WoWs reaction to our queries on addon load (they differ based on many factors). We are aware of the problem and every report might help us in narrowing the cause down (especially detailed ones like this). So thanks, and feel free to add more details about your "user error" if you remember any. 👍