Here’s a transcript of my chat today with Ally’s helpful rep, “Frankie” (with apologies to Tiller & Yodlee for the misplaced frustrations to-date).
TL;DR—They broke things while implementing their new “buckets” feature, they know they’ve broken things, and they’re working on it.
Chris Lozac’h at 14:51, Feb 6:
Hi Frankie. As detailed at the link below, Ally Bank has been blocking Yodlee synchronization for weeks now, and it’s gotten extremely frustrating for me and a number of your other customers.
I’m wondering what can be done to alert Ally’s software dev group in order for them to prioritize whitelisting Yodlee’s IPs for access. (For context, Yodlee’s data syncing is something that used to work, but stopped working in January.)
Frankie at 14:54, Feb 6:
I apologize for the inconvenience. I can certainly answer your questions. Our backend team has been working actively to resolve this recent issue. Yodlee is not the only program affected, in fact I believe most 3rd party aggregators has been affected. I have spoken with people using, Mint, Personal Capital, Wells Fargo etc. I believe the reason it was halted was because we were making some big updated which include the new bucket feature we have.
Once the new features have been optimized and confirmed as working efficiently perhaps the access will be restored. We don’t have much information on this topic just yet.
Chris Lozac’h at 14:55, Feb 6:
Good to know. Thanks for the update!
Frankie at 14:56, Feb 6:
You’re very welcome. We apologize for the inconvenience this has caused.
Chris Lozac’h at 14:58, Feb 6:
No worries. It’s useful to know what’s going on! (And perhaps worth sharing with the dev team that situations like this might benefit from a message right in our accounts so we don’t have to waste our breath complaining to companies that can’t do anything to resolve the issue.)
Frankie at 15:00, Feb 6:
I will definitely forward this information for you. We appreciate the feedback as it is a way to improve our existing services and introduce a new features, like the recent buckets.Thank you very much! Much appreciated.
Sounds like (and this is pure speculation on my part) the Ally devs made some architectural changes touching so many pieces at once that they couldn’t just roll back the buggy code due to the risk of breaking other things that we would probably care about even more than data portability. Again, that’s just pure speculation based on my experience on software teams. Grain of salt, and all that…
Hang in there, y’all! ♂