{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/14/2024 9:24:21 PM
5
-
It’s crazy to me that we haven’t even gotten a response on a working week day!
-
yeah im not too bothered, but it doesnt take a genius to figure out this is obv a server side issue seeing as most of the help forum posts are about it... idk why they keep referring people to the page as if most people havent already looked up the code and tried to fix it themselves. But im pretty sure they have to be at least investigating it now because of the "spike" in posts. Hopefully they fix it soon, but im sure this stuff isnt easy to mess with, so i try to give the benefit of the doubt
-
After ten years and lots of money, I’ve stopped affording the benefit of the doubt. Maybe Ol’ Pete could do with one less expensive car so they can afford decent tech support.
-
thats fair, but as they say the -blam!- always rolls downhill. getting mad at the workers on the ground for these kinds of problems is imo a fruitless gesture but its also not completely unreasonable to expect people to do their job either. For now, im just going to wait and see. They reasonably should say something about it soon, and at least say theyre working on it. If we don't hear any acknowledgement by tmrw and the problem has gotten worse, then I will be irritated and frustrated. But to each their own. All in all, I just wanna grind my weekly story missions for marks dammit!!!
-
I don’t blame the workers unless there’s a clear case for it. I do blame the mid-level managers who probably didn’t allocate enough support to cover today’s shift. No clue how their internal structure works, but the lack of communication is inexcusable. They have more than enough data to understand this isn’t client side and it’s been almost 6 hours since the issue was first reported. They need better processes.
