I am getting this error message while trying to search for a member who has not posted in several months.
Can you fix it before the Australian Open starts?Hey guys,
The tech team is aware of this situation and is looking into it.
Please be patient as we get this resolved!
Case: #2879297
Sorry for the inconvenience everyone
Ed
You've been stating that for some time now. Perhaps it's time to tell your company to get a new tech team. There is no even nearly valid reason that it should take this long to isolate and correct this issue. None.Tech is still looking into this. Is affecting multiple that's why it's taking longer to figure out. We'll let you know as soon as there's an update.
Niall
Update?I have bumped the issue with the tech team and have reminded them that this issue has been ongoing since November. This issue has popped up on a few different sites, so the team is trying to investigate what's happening with each affected site and check for correlations. Thanks for your ongoing patience and we do understand that it's wearing thin. Hopefully the resolution is in sight.
Cheers,
Erik
I think we all appreciate you being cordial about this. But enough with the platitudes. This is unarguably BS. Even if distributed there is no codebase I can think of, even FB, that would require nearly this much time to isolate and correct such an error.Hey there,
Very sorry for the inconvenience everyone.
Seems like this issue is more difficult to resolve than others.
The tech team is looking into it and we'll notify everyone once it is resolved.
Very sorry for the inconvenience.
Ed
We totally understand that you're frustrated, but it's important to note that we (Admin) are just the "middle man" in all of this, so unfortunately 'platitudes' are really all that we can offer at this time. We have escalated, ticketed and bumped the issue, and that's all that we can do from our side of things. The tech team is looking into the issue, but again, it is happening on a few of our sites so they are trying to look at the bigger picture and understand what's causing the problem. The team also wants to make sure that fixing one thing doesn't break something else.I think we all appreciate you being cordial about this. But enough with the platitudes. This is unarguably BS. Even if distributed there is no codebase I can think of, even FB, that would require nearly this much time to isolate and correct such an error.
Thanks. I know you're doing your part it's the tech time that my ire is aimed at. Let's put it this way - can you imagine a dev team at say Google taking this long to fix any error with an established codebase?We totally understand that you're frustrated, but it's important to note that we (Admin) are just the "middle man" in all of this, so unfortunately 'platitudes' are really all that we can offer at this time. We have escalated, ticketed and bumped the issue, and that's all that we can do from our side of things. The tech team is looking into the issue, but again, it is happening on a few of our sites so they are trying to look at the bigger picture and understand what's causing the problem. The team also wants to make sure that fixing one thing doesn't break something else.
I will bump this ticket again as a gentle nudge to the team. Again, we understand that the search function is an important feature of the site and we do apologize for the inconvenience.
Cheers,
Erik
But that just means the problem still hasn't been fully isolated. I mean come on man, running a deep trace on the code and its movement through your servers and accelerators doesn't take nearly this long.What should be working to fix this, isn't for some reason. It seems like it should be straight forward repair job, but it's resisting our attempts so far.
Kevin