Re:Wells Fargo double charged everyone on their bill pays today
by bridanp on Thursday January 18, 2018 @12:01AM
(#16174824)
Unfortunately I was part of one of these at a much smaller bank in the past. A job that "memo posted" checking accounts failed. When we restarted the job, we tagged the restart to the wrong step. We should have hit the restore step first, prior to the posting failure. Instead, we tagged the one right after, duplicating the posting for all accounts that had successfully passed on the first run. It was thousands of transactions that had to be backed out before they were hard posted. It was an awful feeling when we realized it, made more awful to know we caused people so much trouble that day. Anyway, I'm telling the story because it doesn't have to be because Wells Fargo is inherently bad. Their management has made some significant errors lately that could be considered criminal. But in this case, I'd side with it being program, job scheduling, or technical admin errors. I'm almost 100% positive the people responsible are just sick about it right now.
Re:Wells Fargo double charged everyone on their bill pays today
by bpchaps on Thursday January 18, 2018 @02:15AM
(#16175311)
Hah! Yeah, probably. No ops person I've met has NOT made this mistake. The more you touch, the more likely you are to break something. It's bound to happen eventually. So, when it does, you buckle down and hope that ALL_CAPS_REG_JOB_X-22 wasn't that important.
A NOC I worked at used to send company-wide pages (in 2008..) whenever something important broke. "Inadvertently" was used maybe once a month!
Now they should be having a chat with their BAs and their Finance on how to reverse the duplicates.