![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Well, that would explain a few things...
Apr. 14th, 2009 11:58 amAmazon...well, you know, THAT problem...somewhat explained.
In all honesty, this explanation does make a lot of sense to me, as it sounds very much like a system screwup (manmade or otherwise) that might have happened at my own job--I've seen it happen before, and that's why I have the job I have, to catch it when it DOES happen and try to fix it. Apparently, data entry error upstream was the culprit, and the screwup just flowed downstream and caused the whole thing. As they say, the system is only as smart as the person who programmed it.
I'm actually kind of impressed that they mention it being a "Sev-1" issue--that's something we would have done in the same instance.
In all honesty, this explanation does make a lot of sense to me, as it sounds very much like a system screwup (manmade or otherwise) that might have happened at my own job--I've seen it happen before, and that's why I have the job I have, to catch it when it DOES happen and try to fix it. Apparently, data entry error upstream was the culprit, and the screwup just flowed downstream and caused the whole thing. As they say, the system is only as smart as the person who programmed it.
I'm actually kind of impressed that they mention it being a "Sev-1" issue--that's something we would have done in the same instance.
