I view the Institutional Alerts page as more advisory than authoritative. 
1 Like
Yeah, I’m thinking it might work if it’s on list, but it still hasn’t gone through the full verification cycle at Yodlee to remove it.
Yep. From my perspective, I’ve already incurred the pain of cleaning up the duplicates, so now I’m going to keep on filling and refreshing as long as it seems to be working.
I did a refresh today. Required Password. The fill was fine no duplicates were created.
2 Likes
This made me think that if we can get Yodlee to clean up the data on their database before people refresh their Ally accounts (if they haven’t already since this issue started) that will prevent others from having to deal with the duplicates. We’ve asked them if that’s something they can do but first they have to acknowledge they actually caused a problem 
1 Like
Yes, exactly, I’m planning to test if they’ve cleaned the Ally data once they get removed from the Institution Alerts, because I haven’t refreshed it in 14 days (before the duplicates started occurring). So, I haven’t had to deal with the duplicates yet 
My hope was that they’d do a clean up process automatically when these alerts occur, without Tiller prompting. Then it would make more sense that auto-refresh is getting disabled.
1 Like
We received an email back from Yodlee that they have cleaned up the duplicates in their database @Mark.S - there isn’t a way I can truly validate this as I don’t have Ally accounts. Would you be brave enough to try and let us know?
3 Likes
It has been working fine for me other than having to manually update in the console with text code.
1 Like
Nice, I appreciate you sharing that info @heather and that’s my plan, but Ally Bank’s alert got extended to 8/17, so I’m inclined to wait to reduce the variables 
1 Like
I decided not to touch anything while the Ally situation settled down. I just reconnected the account and synced in the new data without issue. I didn’t notice any duplicates, nor missing transactions.
3 Likes
@jawbits had you refreshed before and got duplicates? or this is the first time you’re refreshing since this mess started?
I had not refreshed, or really touched anything, since the moment I noticed that Ally was disconnected (thank you “Hello, Money” emails!). I immediately found this post where people were having a bad time by messing with things and decided to wait things out until yesterday.
1 Like
I’ve been noticing sync issues for Ally for about 2 weeks. I’ve been reconnecting every time it goes out of sync for more than 3 days with a 2FA code texted to me. I haven’t noticed any issues with transactions getting duplicated, but I only have one Ally account and don’t have many transactions. Commenting to follow the sync issues!
@heather I’ve been watching and waiting as this plays out… I have a few Ally accounts and have not synced since before the issue started. If you’re still wanting a guinea pig let me know… otherwise I’ll wait until the institution alert is gone.
Welcome @Snaileb, 
We’re pretty confident that if you haven’t refreshed since before the duplicates were introduced into our system that if you refresh now you won’t get the duplicates. New duplicates aren’t being introduced for more recent transactions. The site alert may mean you have an issue refreshing the institution, but since it’s labeled as “User action required” we think it just means they’re enforcing 2FA now.
So if you don’t mind giving it a try that’d be helpful to validate our assumptions.
1 Like
Makes sense and the alert Issue Start date changed from 7/18 to 8/14, so it does seem like the duplicate issue has been replaced by an auto-refresh issue.
So, I did decide to manually refresh Ally Bank this morning (8/15) and I did not have any duplicates, all the data looks good to me. Looks like Yodlee successfully cleaned up the data 
My last refresh before today (8/15) was 23 days ago on 7/23, before the duplicates were reported in this thread on 7/26.
I hope they do re-enable auto-refresh, including 2FA accounts
And, please Ally and Yodlee come to an open banking agreement 
2 Likes
As the one who started this thread, I’m calling @Mark.S’s post as the resolution of this for now. May we never have to reopen this topic. . .
5 Likes
I have two Ally accounts. One incorrectly had a duplicate transaction in June and again in July.
I refreshed my Ally accounts earlier and the duplicate transaction is still present. Must I manually delete the transaction for June and July? Thanks.
Yes, you’ll have to manually delete them. Once something is downloaded to your sheets, Tiller can’t pull it back. In response to this mess, Yodlee was eventually able to delete the duplicates before Tiller had downloaded them into its database (which then feeds into our sheets). But if they are in your sheets, then they are well past the point at which Yodlee intervened.
1 Like
Thanks @heather,
Just refreshed and can confirm I am seeing the same behavior as @Mark.S … MFA required, but no duplicate transactions that I can find. 
For reference, inside my main ally login I have 2 savings accounts and 1 Roth IRA that I regularly sync. So I would have expected at least some duplicates between the savings account if the issue were persisting.
2 Likes