Did a refresh just now, I still have all the duplicated transactions after rolling back my google sheet and re-syncing the transactions. Seems like whomever is at fault has either a) not fixed it, or b) didn’t clean up the error after the fact. I don’t have any transactions for today (7/31) yet, but as of 7/30, they’re all duplicated.
In fact, I just went back to look and I have transactions duplicated as far back as 6/14, from before I even started using Tiller. I’m not really interested in sorting through a month and a half of 12 duplicates per transaction. I’ll just have to keep reverting my sheet until its fixed? Not sure the path forward here, would be nice to have some update from Tiller staff on the issue.
Reverting the sheet won’t help because the duplicates are already in our database (and we don’t do anything to clean them up in there right now) so you’ll need to manually clean up the duplicates. If you revert and refill you’ll just keep getting the duplicates.
New Tiller user here - Still not able to link our Ally account. It did trigger a 2FA (which I don’t think it was doing earlier this week) but then we got a “Technical error” message. I saw a few other folks saying it’s working for them now, but it’s still not working for us.
Do you know if Yodlee does something to clean up the data?
i.e. say the data hasn’t been transferred to Tiller via a refresh, yet, and the next refresh occurs after the institution has been removed from the alert dashboard
I have some 1200 lines of duplicated transactions. I quite honestly don’t have the time to sort through those. It would probably take hours. Is there any plan to clean up these duplicates in the database? What is very strange to me, is that transactions are duplicated that weren’t duplicated before. It wasn’t just new ones.
There isn’t even a way, at a glance, to tell which line is the “real” one. I’d have to sort through 1.5 months of comparing Tiller transactions to my various bank statements. Being a new user, I’m still on my trial and unfortunately I can’t pay for the service until this is resolved. I really want to, this is a really awesome tool, but right now its simply unusable for me.
With all due respect, @heather, I think that the Tiller Team really needs to prioritize cleaning up data when these issues occur. Otherwise, it erodes the confidence in Tiller (not Yodlee) by Tiller Customers. It was super frustrating to have to clean up data manually and get no more than a shrug. How is Tiller going to prevent these issues from re-occuring so that I can continue to have confidence in Tiller and want to renew again? I like Tiller very much and there have been more pros than cons over the last few years, but…
Just in case someone would like to know the options to remove duplicates within Excel or Sheets. If not for this major issue, maybe a good reference to have.
YouTube videos with Chapter timestamp in descriptions.
I’ve been having the same issue, both 2FA required and transactions duplicated across both of my accounts (fortunately only the two, and not very active).
@Mark.S yodlee does clean up the data on their side, we just don’t respond to those changes at this time. It’s a big lift for us to be able to respond to those changes appropriately because it’s a type of change management. They send a “delete” notification for one of the duplicates. Our system doesn’t do anything with this information. We’d need to both 1) respond to the delete notification by deleting the corresponding transaction in our database and 2) remove the data from your spreadsheet. The 2nd point there is the bigger lift that has a lot of implications because we don’t touch or modify the data once it’s in the spreadsheet, any modifications to the data in the spreadsheet once we fill it there are a result of actions you are taking (e.g. running AutoCat).
@atkinson21 I would recommend reviewing the Date Added column out right in the Transaction sheet to see if it helps. If it was a big batch that came in at one point that could help you clean up a lot of them. Otherwise I recommend checking out this community-supported tool: Docs: Manage Duplicates workflow
Earlier you’d said that when I roll back and re-sync it won’t work because the duplicates remain in the Tiller database. A rollback and re-sync would work if Tiller did process the delete. Is there a reason point #2 is necessary? Let the user decide if they want to “remove the data from the spreadsheet”. Would having the duplicates in the sheet, but not in the db be an issue?
Fwiw, I’m supportive of the conservative approach that Tiller takes on this issue. Having to remove duplicates is, in my view, much less problematic than a situation in which a transaction thought to be a duplicate is inadvertently deleted before it even makes it into our sheets (and with whatever tool is used, there is very likely to be inadvertent deletions). This Ally situation was a mess, but it was a mess that ultimately took me about twenty minutes to clean up (with 420 duplicates the first time it happened). Reasonable people can disagree on which mess is preferable, but I just wanted to chime in to say that it’s not clear to me that Tiller should be changing how it manages the data it receives from Yodlee.
It’s just a better user experience than having to do a rollback. What if you’d categorized a bunch of transactions for a different account that didn’t have duplicates? You’d lose all those changes and have to re-do them.
Thanks for your thoughts here @dmetiller - it’s a good point that inadvertent deletions could happen (where yodlee gets it wrong and sends us an unnecessary delete notification). Just more to ponder when we get around to thinking through whether we want to process those notifications and “update” notifications, both of which would allow us to support pending transaction data in the future.
I had a bunch of duplicates that were created a few days ago, I went through and manually deleted them. It was a total pain, however I got it done and confirmed it’s accuracy with some reconciliation. So, I thought we were done with the Ally bank issue. However, today, 614 new transactions (of which most are duplicates).
It won’t be that hard for me to go through and delete all 614 transactions because I’ll just delete all transactions for today, but then I have to figure out which ones are actually original transactions and which ones are duplicates. And then re-reconcile.
I sure hope this gets fixed soon. We have about 9 accounts at Ally, it is our primary bank, and this is a massive headache.
For anyone paying attention, the duplicates go as far back as 8/21/23.
I was also affected by the Ally issue but, having found this thread, stayed clear of trying to fix the issue or resolve any connection issues (for fear of duplicates). It’s unclear to me if there’s still an underlying issue or whether I’m probably safe to fix the issue and sync up?
(Also, IMO Tiller should remove known duplicates from their database. That way if folks do want to just rollback their sheets, they could choose to do that. I think it would be obvious to most folks that doing so would result in the loss of any other changes they’ve made to their data after the checkpoint they’re rolling back to. Leave it up to users to weigh which is less work for them in their situation).
What I might do if I were you is add another column for all your existing transactions, put an X in it, then sync.
All your recent stuff, hopefully, won’t be duplicated (but maybe). The older stuff that duplicates, you’ll have an x in the column to know it’s original, and you can delete all the transactions without an X.
I’ll likely sync every day so the magnitude of the impact will be lower and less to unwind.
My sense is that a takes a couple of days for all of the duplicates to clear out. At least that was the case for me, and my Ally accounts are acting totally normally now (except for the addition of 2FA). Ally is my primary bank as well, so I’m glad I just dealt with the problem and moved on. Regrettable that it happened and annoying to deal with, but hopefully in the rear view mirror now.
That’s what I thought until I sync’ed today, 600+ duplicates. From what @heather said above, Tiller isn’t removing duplicates from their system due to down stream issues they create, so even if the problem is solved on the Yodlee/Ally level, it exists inside the Tiller DB.
Right. Once they are in Tiller’s database, they aren’t going anywhere until you’ve dealt with them. I haven’t had any additional duplicates in probably four days after having a few hundred for a few days in a row. I am hopeful that means that no additional duplicates are being passed from Yodlee to Tiller.