Vendor caching is f'd #844
Labels
bug filed
A bug has been filed in BNet's internal bug tracking system for this request/report.
bug
ready for release
I got a report today and was able to confirm that Vendor caching isn't behaving properly. If you request two characters' vendor data on the same account before our 60 second cache has expired, you'll get the vendor data from the first character that you happened to request.
This will be fixed in the January deployment!
The text was updated successfully, but these errors were encountered: