Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to export all accounts for balance history #44

Open
tomshaffner opened this issue Dec 12, 2023 · 4 comments
Open

Failed to export all accounts for balance history #44

tomshaffner opened this issue Dec 12, 2023 · 4 comments

Comments

@tomshaffner
Copy link

tomshaffner commented Dec 12, 2023

Worked great for transaction exporting, but when downloading account balances it failed for 30 of 105 accounts. My console in this case shows this:
Screenshot 2023-12-12 113146
Interestingly, in the case of one of my banks the balance history I get includes some of the accounts at it but not all of them, so it doesn't seem to be bank-specific.

A look at the verbose debug screen gives this:
image

@tomshaffner tomshaffner changed the title Failed to export all accounts Failed to export all accounts for balance history Dec 12, 2023
@idpaterson
Copy link
Contributor

I suspect that one or two of the improvements in #30 could fix this for you. While my code has not yet been reviewed by the Monarch team, if you are willing to give it a try I have published a prerelease here. If you would like to give it a try, please click that link then under Assets download the chrome-extension.zip file and extract it. Then follow Monarch's instructions here for installing the unpacked extension starting at step 2.

If you decide to give it a try I am interested to hear if it works better!

@bertique
Copy link

This saved me. I had already migrated to CK and was hitting the rate limit with the latest official version for downloading balances. This downloaded balances for all my xx accounts without an issue. Thank you!

@idpaterson
Copy link
Contributor

idpaterson commented Jan 26, 2024

I'm glad it helped! Interesting result though because all of the bug fixes in that code were submitted separately earlier in January and incorporated into the official extension release version 1.0.8. Do you happen to know whether it was the latest version 1.0.8 on the Chrome web store that was getting rate limited, or could it have been an earlier release? I could have missed something important if 1.0.8 doesn't work for you.

@bertique
Copy link

Yes, it was on the official 1.0.8 from the web store. Though I just tried again and it was successful with the official app, so not sure what happened earlier. I did get logged out after about 4 accounts and then when logging in, it just showed a page that said something like the service is not available right now. I assume that means I was rate limited, or some other transient issue on the Mint side I assume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants