Open MagicLegend opened 4 months ago
Hi Magiclegend,
Haha, indeed it looks like YNAB rejects 5 year old transactions. One option is to exclude the offending account from the "accounts" section in your configuration.
I've also added a commit to not go back further than 5 years: https://github.com/wesselt/bunq2ynab/commit/ba06874621409393074a500c96b81c950ae3165a
Kind regards, Wessel
Hi Wessel,
Thanks for the quick fix! What would be the best way to get the lambda updated? Or is it automatically the latest version of master
when I reinstall the application from the repository?
Thanks!
Updating the lambda was discussed here: https://github.com/wesselt/bunq2ynab/issues/49
It takes some expertise at AWS which I don't really have. I've been planning to learn it for a few years now 😂
Gotcha, I see. I also don't have the expertise I'm afraid, I was using this project as an excuse to learn some about it 😄 Let's follow up in #49 about updating the AWS app?
Since last night (execution at 1AM last night was the first time this happened), I'm unable to sync my transactions:
I think I found a limit in the YNAB API that wasn't accounted for :-)
<accountThatDoesntExistAnymore>
is an old account that I can't find in my Bunq app anymore, since I replaced it with a savings account. I did still have it in YNAB but it was simply empty containing no transactions. When logging at DEBUG level I can see it's trying to create a transaction that happened on2019-01-29
, which is more than five years ago now.Archiving the account in YNAB did not seem to solve it, it still fails when manually trying to execute the sync.
Any tips on what I could try?
Thanks!