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.