503 thrown when fetching transactions on large budgets
complete
Brandon Trautmann
Some users are unable to use Lumy because they have large transaction histories (most often we see this for users with 25k+ transactions). The API throws a 503 in these cases, meaning Lumy cannot load their data.
The API team is aware and has limited resourcing to fix. Unfortunately workarounds are not obvious. I did a rundown of the options and why they don't work in this reddit post.
Brandon Trautmann
complete
This has been confirmed to be fixed by YNAB and I have one user reporting they are now able to access Lumy when they were previously blocked.