This could be isolated to just this zone but I've been slowly working on loremasters the last couple days. After 9.1.5 and the latest ATT on Curse, I cant seem to get the quest titles to show up instead of numbers. /reload and Rebuilding the collection doesnt seem to work.

Yea, a huge bloat to the database for ATT to need to capture and hold onto the names of 30,000+ quests, in every WoW localization mind you just to not have the 'Quest ###' show up after server restarts. It just asks Blizzard servers nicely for the name, and the server only has a name to provide if the quest has been cached into the server itself at some point since it was restarted. So usually on Tuesday/Wednesday, many quests will have this situation occur.

If it is actually getting a name and THEN reverting back to 'Quest ###' that's clearly a bug and will need to be investigated. Replicating the issue for testing will of course be very difficult...

Thanks for the detail, didnt mean to be snappy, that makes a bunch of sense (especially localizations).

I cant be 100% for sure that it has the title and then snaps back to the Quest # but I think it happened. Let me ask you this. If I was questing yesterday before reset and had all the quest titles, and then I play after reset, do they reset because I dont have the most up to date info? or would it use old data?

Im going to keep doing some of these quests and see what happens. Like the follow up to https://www.wowhead.com/quest=27415/the-brood-of-onyxia is a quest #. Gonna see if it clears up when I pick up the quest.

Yea, a huge bloat to the database for ATT to need to capture and hold onto the names of 30,000+ quests, in every WoW localization mind you just to not have the 'Quest ###' show up after server restarts. It just asks Blizzard servers nicely for the name, and the server only has a name to provide if the quest has been cached into the server itself at some point since it was restarted. So usually on Tuesday/Wednesday, many quests will have this situation occur.
If it is actually getting a name and THEN reverting back to 'Quest ###' that's clearly a bug and will need to be investigated. Replicating the issue for testing will of course be very difficult...

Thanks for the detail, didnt mean to be snappy, that makes a bunch of sense (especially localizations).

No worries, it's asked quite a lot as it's definitely weird that it seems to users that quest data is disappearing from one day to the next without any changes on their end.

I cant be 100% for sure that it has the title and then snaps back to the Quest # but I think it happened. Let me ask you this. If I was questing yesterday before reset and had all the quest titles, and then I play after reset, do they reset because I dont have the most up to date info? or would it use old data?

It's not on your side that the data has an issue, and ATT isn't caching the quest names locally for you between play sessions.
Prior to Tuesday, the Blizzard servers had someone in the game who interacted with the NPC, or logged on with the quest in the log, or something which caused it the information on that quest to be loaded into the server. With Tuesday's patch, they restarted all their servers, which wiped the cache of all quests. Since then, no one has caused the server to load the given quest, so when ATT requests that information, the server just shrugs and says 'idk' and we are left just displaying 'Quest ###'.

Im going to keep doing some of these quests and see what happens. Like the follow up to https://www.wowhead.com/quest=27415/the-brood-of-onyxia is a quest #. Gonna see if it clears up when I pick up the quest.

ATT does cache quest names during a play session, so if it fails to load the name, then you pick up the quest, I'm not sure that it will immediately update with the name. But if you do a /reloadui after picking up the quest, the name should now be available from the server and will get populated correctly in the list.

Hello! That is probably because no person on the server has those quest in their log or completed them after reset.

Seems to be happening on my main too. What's interesting is that it will retrieve the quest title and then flicker back to the Quest #. So far I see it on quests that are older than Shadowlands (it could be happening on SL stuff too but I've done a bunch of them already.

Hello! That is probably because no person on the server has those quest in their log or completed them after reset.

Odd. if that's how the addon handles retrieving quest titles, that seems super reliant on factors out of a players control. They arent super new quests too or anything. People have had to have them completed for years now.

Ill also highlight that it will have the right name and flick back to Quest #.

Yea, a huge bloat to the database for ATT to need to capture and hold onto the names of 30,000+ quests, in every WoW localization mind you just to not have the 'Quest ###' show up after server restarts. It just asks Blizzard servers nicely for the name, and the server only has a name to provide if the quest has been cached into the server itself at some point since it was restarted. So usually on Tuesday/Wednesday, many quests will have this situation occur.

If it is actually getting a name and THEN reverting back to 'Quest ###' that's clearly a bug and will need to be investigated. Replicating the issue for testing will of course be very difficult...

Ill go ahead and see myself out then :P

Thanks for the explanation! Makes a bunch of sense! Hope you have a nice day :D