4 ms·
Obviously having something like this happen sucks. If nothing else, you should be able to have a specified timetable for updates (every 4 hours, for example),
by tallanvor 14y ago
Obviously having something like this happen sucks. If nothing else, you should be able to have a specified timetable for updates (every 4 hours, for example), even if it's just "we're still analyzing this issue" or "we are evaluating potential solutions".
That said, when you're dealing with a cloud-based application, fixing a problem like this is not going to be easy. First they need a clear enough understanding of how this happened to prevent it from happening again. Next you have to start coming up with scripts to correct the issue. After that you have to test the scripts to make sure you don't make things worse. Finally you can update production.
Most likely the support team has engaged an operations team and probably some developers as well. But even if they've been working through the weekend, there's no guarantee that they'll have a solution yet.
Or maybe Google doesn't have the necessary people on call over the weekend so nothing has actually been done. I can't say.