I’ve reached out to support and all that seems you do is send us more of the same articles. We have already used those and need a better solution. This transactions sheet is the heart of the spreadsheet and needs to work properly.
@alkrongold, I just reached out to you via the support thread you have open to see if we can get to the bottom of this. The day we pushed the changes to the Account Summary on the Console we also pushed an update to the Tiller Money Feeds add-on, which is more likely the culprit for this type of issue.
@heather, I sent you the transactions that came in this morning through the chat feature in hopes that will help get to get this resolved. Did you receive that?
The column is there, but I have never used the function.
No, I am not using statements. I may have the sheet but I don’t use it.
I saw this behavior (duplicate transactions with missing data validation) one day when all these changes were being made. The Update Sheets function took 30 minutes to run that morning - the only time I have seen that take more than a minute or two. I logged OUT of Tiller Money Feeds Setting page, logged out of Tiller Console and closed my Tiller spreadsheet. I then reopened and logged back into everything. It has not duplicated any transactions for me since then.
- You installed the Statements sheet
- You removed the Statements sheet, but left the Statement column intact in the Transactions sheet.
Our team is working on a fix and we’ll post recommendations here when we have an update.
Yes, that’s correct for me, deleted Statements sheet but not Statements column within Transactions sheet.
Thanks for looking into this. I’ll try to delete Statements column and see if this helps at all, while I wait to hear back.
The reason you’re getting duplicates in this scenario is that the Tiller Money Feeds add-on writes the data validation rule back into those columns after it feeds new data in, but since it can’t find the Statements sheet it crashes on the re-writing the rule and then it doesn’t know where it left off adding transactions (in come the duplicates).
The fix for now is to remove the Statements column from your Transactions sheet (right click the column header to delete it) and then the updates will stop crashing and causing duplicates.
You can try using the Duplicates Manager from Tiller Labs to correct the existing duplicates.
Thanks Heather. Along with the duplicates, for me, the category column stopped including the data validation.
We have reproduced a scenario where a data validation conflict interrupts the Update Feeds script and produces wonky results— notably possible loss of data validation in the Transaction sheet and also possible duplicates.
The problem is caused by data validation conflicts in the Transactions sheet (i.e. the scripts are trying to write in new records that do not comply with the data validation rules in the sheet). I believe our code properly handles the situation where a category is written via AutoCat that is not/no-longer in the Categories sheet and conflicts with the Category column data validation… but the missing-Statements sheet (i.e. data validation to a sheet that is not present) seems to be an exceptional case of this bug and apparently exacerbates the problem. I believe this is a Google API bug as this handling this situation shouldn’t be any different from coding robustly for other data validation conflicts. Nevertheless, we are working on the issue.
In the short term, the easiest fix is:
- Remove the Statement column from Transactions if you are not using it (or at least remove the data validation on the entire column if there are values you wish to preserve), and
- Do your best to ensure your AutoCat rules do not conflict with Transactions sheet data validation
P.S. Regarding the loss of data validation, @fullyspooled, I recommend re-adding the Category column data validation linking back to the Categories sheet using the menu bar.
Just wanted to follow up that we pushed the fix for this yesterday. The sheet won’t update with this data validation issue, but it will present an error instead of crashing in the middle of an update and then introducing duplicates on the next update.
Just wanted to note that the duplicates would be for ALL accounts linked to the sheet, not just a specific institution. If you’re experiencing duplicates for a specific institution, you should review our duplicates guide and then reach out to support if needed.
I don’t use the statements sheet and the duplicates are continuing to happen for me.
The Manage duplicates tool doesn’t catch them either. (Also annoying, the mange duplicates tool seems to forget the unflagged transactions from the past and that requires re-reviewing them).
@lightcap, are these duplicates for a specific account or ALL accounts connected?
They seem to be happening only for two accounts (same bank). Summit Bank in Bend, Oregon.
@heather I think I’ve traced it to the fact that the bank changes the description when the transaction goes from pending to posted. I have no idea why they do it, but there’s some numbers that change in the description.
@lightcap that makes sense and actually isn’t too unusual for some institutions. We hope to be able to address that in the future, but it’s a ways out. I’d recommend just removing one of the instances. We haven’t had much luck with our data provider correcting duplicates like this.
Also, closing this topic because the original bug that was causing this has been fixed. If others are experiencing duplicate transactions please review our guide on duplicates reference here and use the chat to let our team know if they’re persistent for more than a week from today (i.e. the day you’re reading this )