MD+ downloads stopped working today?
Is this just me, or others? Another Plaid problem?
MD+ downloads don't work this morning. They worked fine yesterday. They seem to hang mid-download, and then it locks up the MD app later.
Click on an account
Choose Download Transactions
See message "Downloading (account name).... at the bottom
Nothing else happens. No "Downloaded X of X transactions" at the bottom status like usual. After 10 seconds the status area goes blank.
Then downloading any other account doesn't do anything. But basic use of MD is still working like normal, the app isn't fully locked up.
Then when quitting MD, I get "Finished saving data" dialog, then nothing. Doesn't fully quit, have to force quit. As if some process is still running that won't allow quitting.
This happens in two totally different MD data files.
Using v 2024.1(5118) on MacOS 14.6.1 (but the problem happened in 14.6.0 before I applied the upgrade). Yes, I've rebooted.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by andyschmid on 20 Aug, 2024 04:44 PM
I am dealing with this exact issue right now. I have also tried rebooting, closing out MD causes it to sit there on the "Finishing saving data" dialog.
Moneydance 2024.1.5118 on Linux
2 Posted by david.beav on 20 Aug, 2024 04:49 PM
More data:
- If I open MD and do some stuff and quit, without doing any Downloading, it quits normally
- In Console window, when I choose Download, I just get "20240820-09:44:33.682: Online downloads (account: 'xxx', service: 'Moneydance+') started...", nothing else.
- It worked one time? Had lots of useful stuff in the Console and it clearly worked. But second try didn't work.
- Right now, after getting "Online downloads started..." in console and nothing else, twice, 20 seconds apart, it showed "JVM Maximum memory possible, total memory allocated", but nothign else for 30 min.
3 Posted by dtd on 20 Aug, 2024 09:29 PM
Responding to three threads. Composing message now.
4 Posted by dtd on 20 Aug, 2024 09:53 PM
First, my downloads are working. So, I can only rely on information provided, which for all threads, is good information.
I use a Macbook Pro Sonoma 4.6.1 2024.2(5146); I've also tested with (5118).
3 of the 4 comments about freezing are also on Macs, 1 on Linux.
From what I can tell, there appears to be a Java issue (but I'm not real savvy on that, but may set what others look at).
That said, here are some other takeaways I had, looking over the messages.
1. It's not everywhere, so specific things need to be looked for.
2. Normally, you get a specific message from a bank when it fails to download, like you could report an error message the bank sent.
3. It sounds like it might be a specific bank or banks that are not providing what would trigger an error, but is erroring in a circular fashion causing a loop. They do often send messages about Java themselves.
4. This is all conjecture on my part as I don't read error logs like some can.
So to particular posters:
@david.beav - you appear to have good analysis, and I think a tester would be helpful. First, can you identify if there is a particular bank involved (i.e. looking at the bottom status line, can you see if it freezes on a particular bank (and you might identify "it's the next bank" if it freezes on one, but has "moved" to the next one)
The freezing on closure suggests it may be a bank in some kind of loop.
I'd ask for all your banks, but that's not kosher, so just an examination, especially since this is a theory.
Also could you upgrade to preview 5046? A lot of options have been added to the console window (optional) and a lot are about showing ofx, showing MD+ messages, etc. - you can probably figure out what you need to check, but ask if not clear.
-------
@andyschmid - same song, different verse. if willing, I'd ask the same as david as a linux test - if not comfortable with that, just wait for other results, my thoughts changing, etc.
-------
@david.atherton - seems like everyone gets the same results - finding a common failing bank between the four of you might be helpful.
--------
@jvspringrose - all four of you have the same issue - apparent freeze, but not solid, closure of syncing upon closure of moneydance (or termination of one download)
I'm sure there are more with this issue, but it does work for some/many - I suspect a bank gone wild on this. (which could mean it will fix itself, but I'd like to identify what bank and what happens if it persists (and I'm correct in my thoughts)
5 Posted by dtd on 20 Aug, 2024 10:00 PM
Oh, and if I possibly sound official here, I'm also a user and not associated with MD/IK
6 Posted by dtd on 20 Aug, 2024 10:04 PM
Oh, one question: is this just MD+, or are you also using OFX?
I use both, and OFX wasn't particularly mentioned by anyone. If only MD+ users, it could be Plaid that has gone wonky, but then I'd expect more complaints/questions - again, unless it is a particular bank in MD+
7 Posted by david.beav on 20 Aug, 2024 10:05 PM
I just posted a reply but where did it go?
1) Thanks dtd for helping
2) Sorry, it's not specific to banks. Although it worked one time with Amex just now and locked up the next time, it basically doesn't work with any of my accounts:
Chase bank
Pacific Premier Bank
Gulf Winds Credit Union
Chase, Citi, Capital One and Amex credit cards
And I don't use OFX any more at all, this is all with Plaid
8 Posted by david.atherton on 20 Aug, 2024 10:09 PM
David.Beav describes my problem exactly. I've re-installed 2024.1. Then 2024.2. The app often freezes on "Finished writing sync data" and then I have to completely re-boot the entire Mac.
It isn't any one particular bank. I've started with Bank of America. After re-start. Chase. Then after re-start AMEX. Same on all of them. Nothing downloads.
Not using OFX either; all with Plaid
Yesterday OK. Today IMPOSSIBLE.
9 Posted by david.beav on 20 Aug, 2024 10:12 PM
Also: you meant preview build 5146, not 5046
10 Posted by jvspringrose on 20 Aug, 2024 10:13 PM
To: David.atherton. I found that I do not have to reboot the entire Mac, but that "Force Quit" frees the rest of the computer. It has no effect on the problem, however
11 Posted by andyschmid on 20 Aug, 2024 10:14 PM
This just started today, and there have been zero software updates on my system since it was working fine yesterday.
From my experimenting this seems like an intermittent connection issue somewhere in the plaid pipeline. The connection timeout does not seem to be handled well by moneydance software, which continues blocking until it eventually fails and moves on to the next bank.
12 Posted by david.atherton on 20 Aug, 2024 10:18 PM
Occasionally Force Quit works, but more often than not it freezes my entire Mac.
But only if I’ve tried to download. Regular data entry still works correctly suggesting a problem with Plaid, particularly as 12 hours ago it was working perfectly.
13 Posted by david.beav on 20 Aug, 2024 10:27 PM
Force Quit always has worked for me.
Preview Build 5146 seems to be better than the previous build, but it still is having the problem. E.g. I can choose one account and Download and it works, then it fails the next time.
When it fails, I only get this in the Console:
20240820-15:21:38.575: Online downloads (account: 'xxx', service: 'Moneydance+') started...
When it works, the next line after the "started..." line is:
20240820-15:21:21.948: it took 0.009 seconds to build a plaid client
... and then lots of log lines of what it's doing.
So my gut agrees with Andy's, that something is failing when trying to build a Plaid client, and it's gotta be downstream since it's happening to many of us.
Is anyone at MD aware of this thread?
14 Posted by jvspringrose on 20 Aug, 2024 10:37 PM
(My replies are dropping off, too). I agree about this likely a Plaid problem. I was able to re-link my accounts and institutions, even receiving confirmation from BOA, but still no help to the problem. Don't know if MD knows, or how to alert them.
15 Posted by dtd on 20 Aug, 2024 11:00 PM
Ok, "not a specific bank" - sure that's possible and it is a Plaid problem only.
Have any of you tried downloading only from a single bank? (Pick Chase CC if possible, as that works for me). You'd pick the bank/CC, then go to online/Download just that bank (8th choice).
If it is indeed all banks, this won't work for any bank. Try it for 2-3 of your banks/cc and see if it fails for all of them.
Not telling anything - just trying to properly diagnose.
Thanks.
16 Posted by dtd on 20 Aug, 2024 11:02 PM
As for does MD know, they might learn from this thread, but unless it is universal (versus 4 so far - could be others) they wouldn't know, and would probably rely on more complaints/threads to learn.
It is also midnight in the UK at the moment.
17 Posted by dtd on 20 Aug, 2024 11:04 PM
As for intermittent connection issue with Plaid, that is certainly a possibility, but it seems like it would be more pervasive if so. Like mine wouldn't work either. (I have verified some others do also work)
18 Posted by dtd on 20 Aug, 2024 11:06 PM
Maybe it's geographical? If willing, just something like Northeast US or Florida might reveal something. I'm in Idaho.
19 Posted by david.beav on 20 Aug, 2024 11:08 PM
In in Southern Cal, ISP is Cox Cable. Good ping times to Yahoo.com (56 ms)
20 Posted by dtd on 20 Aug, 2024 11:08 PM
It's always harder to diagnose when outside of Moneydance itself, as neither customer support (nor experienced users) can immediately point to something within the program.
21 Posted by dtd on 20 Aug, 2024 11:22 PM
@david.beav - click the bottom left of the console in 5146, and check everything at the bottom except doable/undoable and costcalculation (a lot of these are syncing bits)
Also still interested in single bank downloads (post 15)
22 Posted by david.beav on 20 Aug, 2024 11:25 PM
Launched MD
Download from Amex credit card... worked
Download Amex again... failed
Launched MD
Download Citibank credit card... worked
Download Citi again... failed
Launched MD
Download Capital One credit card... worked
Download Capital One again... worked
Download Capital One again... failed
Launched MD
Downloaded Chase credit card... failed
When Chase failed, log was a little different than earlier:
Online downloads started
Log setting OFX has been changed to: Enabled
It took 0.012 seconds to build a plaid client
Downloading from Chase Visa....
then nothing, it locked.... EXCEPT... while waiting for the next step from Chase Visa, it interjected 7 rows of "Got accounts for item XXXX URL /mdplus.infinitekind.com/plaid/accounts/get"
And then
Successfully updated MD+ account lists
Ran 1 of 2 MDF tasks
So while the downloading process was running and failing, another process kicked in and seems to have worked.
Hmmmm...
Ah, something new.... after Chase failed, I got this in a Online Error dialog:
There was an error communicating with your financial institution. The details of this error are below.
Bank Name:Moneydance+
Account:Chase Visa 20th **
Account Number:43885760xxxxxxxx
A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server.
Error Description:java.net.SocketTimeoutException: Read timed out
java.net.SocketTimeoutException: Read timed out
at java.base/sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)
at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
at java.base/sun.nio.ch.NioSocketImpl.read(Unknown Source)
at java.base/sun.nio.ch.NioSocketImpl$1.read(Unknown Source)
at java.base/java.net.Socket$SocketInputStream.read(Unknown Source)
at java.base/sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at java.base/sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.kt:379)
at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.kt:337)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:209)
at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at com.moneydance.apps.md.controller.olb.plaid.PlaidConnection$JWTTokenInserter.intercept(PlaidConnection.java:527)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at com.plaid.client.PlaidClient$PlaidApiHeadersInterceptor.intercept(PlaidClient.java:122)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154)
at retrofit2.OkHttpCall.execute(OkHttpCall.java:207)
at com.moneydance.apps.md.controller.olb.plaid.PlaidConnection.downloadBankTransactions(PlaidConnection.java:1260)
at com.moneydance.apps.md.controller.olb.plaid.PlaidConnection.getTransactions(PlaidConnection.java:1223)
at com.moneydance.apps.md.view.gui.OnlineManager.downloadTransactions(OnlineManager.java:649)
at com.moneydance.apps.md.view.gui.OnlineManager.downloadTransactions(OnlineManager.java:630)
at com.moneydance.apps.md.view.gui.AccountDetailPanel.lambda$actionForService$10(AccountDetailPanel.java:460)
at com.moneydance.apps.md.controller.BackgroundOpsThread.run(BackgroundOpsThread.java:177)
23 Posted by dtd on 20 Aug, 2024 11:29 PM
Ok, some interesting info. gotta try to assimilate it to conjecture differently.
24 Posted by david.beav on 20 Aug, 2024 11:34 PM
And... with every log option on as you asked, I started Chase credit card and the only thing in the log is :
20240820-16:32:12.384: Online downloads (account: 'Chase Visa', service: 'Moneydance+') started...
I'm signing off for now but will try to respond to any other requests for info.
25 Posted by dtd on 20 Aug, 2024 11:36 PM
Did you do the click lower left and check most everything BEFORE you did the above? It doesn't appear magically after checking, you have to do it before you attempt things.
I don't see for example any MD+ returned messages for either the individual bank items nor if you tried it all at once (and it freezing).
Also, I note you relaunched Moneydance each time after a failure. Did each failure throw MD into that "force shutdown" needed, or you did it by choice? (If by choice, do 1 bank to failure, then if not frozen, do it again with a different bank.
Console with annotations desired. Thanks.
26 Posted by dtd on 20 Aug, 2024 11:37 PM
Can you do this with all the banks? Sounds like your Chase card might be an issue, but for when other banks worked, the MD+ messages would be useful for diagnosis.
27 Posted by TonyRI on 21 Aug, 2024 12:01 AM
Just to chime in. I don't have any issue with Amazon Chase Visa utilizing MD+, at present, however my Discover MD+ connection just gave a similar error message that @david.beav had received with his Chase Account:
There was an error communicating with your financial institution. The details of this error are below.
Bank Name:Moneydance+
Account:Discover Card
Account Number:Discovr16X1XXXXXXX
A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server.
Error Description:javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at java.base/sun.security.ssl.SSLSocketImpl.handleEOF(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.kt:379) at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.kt:337) at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:209) at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226) at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106) at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74) at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at com.moneydance.apps.md.controller.olb.plaid.PlaidConnection$JWTTokenInserter.intercept(PlaidConnection.java:527) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at com.plaid.client.PlaidClient$PlaidApiHeadersInterceptor.intercept(PlaidClient.java:122) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201) at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154) at retrofit2.OkHttpCall.execute(OkHttpCall.java:207) at com.moneydance.apps.md.controller.olb.plaid.PlaidConnection.downloadBankTransactions(PlaidConnection.java:1260) at com.moneydance.apps.md.controller.olb.plaid.PlaidConnection.getTransactions(PlaidConnection.java:1223) at com.moneydance.apps.md.view.gui.OnlineManager.downloadAllTxns(OnlineManager.java:549) at com.moneydance.apps.md.view.gui.OnlineManager.downloadAllTxns(OnlineManager.java:509) at com.moneydance.apps.md.view.gui.MoneydanceGUI.doNetSync(MoneydanceGUI.java:3281) at com.moneydance.apps.md.controller.uri.Dispatcher$UIDispatcher.run(Dispatcher.java:129) at com.moneydance.apps.md.controller.uri.Dispatcher$UIDispatcher.invoke(Dispatcher.java:78) at com.moneydance.apps.md.controller.uri.Dispatcher.invoke(Dispatcher.java:52) at com.moneydance.apps.md.controller.Main.showURL(Main.java:1010) at com.moneydance.apps.md.controller.BackgroundOpsThread$DownloadAllTask.run(BackgroundOpsThread.java:267) at com.moneydance.apps.md.controller.BackgroundOpsThread.run(BackgroundOpsThread.java:192) Caused by: java.io.EOFException: SSL peer shut down incorrectly
at java.base/sun.security.ssl.SSLSocketInputRecord.read(Unknown Source) at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source) at java.base/sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source) at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source) ... 37 more
:
28 Posted by david.beav on 21 Aug, 2024 12:07 AM
Yes, I turned on all console options as soon as I launched MD.
Yes, every time a connection hangs, I need to force quit. Doing another connection attempt while it's hung has no effect.
29 Posted by TonyRI on 21 Aug, 2024 12:12 AM
Plaid seems to have gone wonky
30 Posted by david.beav on 21 Aug, 2024 12:19 AM
I hesitate to post the ENTIRE console log without knowing what personal stuff would need to be scrubbed. But here is everything in the log after MD is launched and settings are set. I Downloaded one credit card, it worked the first time, and failed the second time before "Building a Plaid Client" should have been there. Actions annotated with ****
*** Started Download
20240820-17:09:15.823: Online downloads (account: 'Citi Costco Visa', service: 'Moneydance+') started...
20240820-17:09:16.585: it took 0.019 seconds to build a plaid client
20240820-17:09:16.586: downloading from Citi Costco Visa, with starting date Wed Aug 14 00:01:00 PDT 2024
20240820-17:09:17.615: Plaid: Transaction: Name -> NLOV485QEA4XQ9Z59L WWW.OVPAY.NL NL; Location -> com.plaid.client.response.TransactionsGetResponse$Transaction$Location@7d81b6b2; TransactionCode -> null; MerchantName -> null; TransactionType -> place; OriginalDescription -> null; PaymentChannel -> online; IsoCurrencyCode -> USD; TransactionId -> qAnrKN4b8ri9rm5zR494Uaa7Mb9KKzh4ornbK; AuthorizedDate -> 2024-08-16; AccountOwner -> xxxx; PaymentMeta -> com.plaid.client.response.TransactionsGetResponse$Transaction$PaymentMeta@15bb9e1f; Pending -> false; Date -> 2024-08-16; Amount -> 7.16; Category -> [Food and Drink, Restaurants]; CategoryId -> 13005000; AccountId -> 9pYx7rDXvxFe73p1R9O9HxwoEXML5qI6KAd9p; PendingTransactionId -> v4ngJX6b8gtOVwa3BmObuOpop0vw3eUDzqrVd; UnofficialCurrencyCode -> null;
20240820-17:09:17.775: received MD+ txn: qAnrKN4b8ri9rm5zR494Uaa7Mb9KKzh4ornbK 20240816 NLOV485QEA4XQ9Z59L WWW.OVPAY.NL NL -716
20240820-17:09:17.775: Plaid: Transaction: Name -> Circle K; Location -> com.plaid.client.response.TransactionsGetResponse$Transaction$Location@57e27bd7; TransactionCode -> null; MerchantName -> Circle K; TransactionType -> place; OriginalDescription -> null; PaymentChannel -> in store; IsoCurrencyCode -> USD; TransactionId -> 0pYnyBjX1nF5XyE3zr5Qcy0a0xOXPwtXo4RAQ; AuthorizedDate -> 2024-08-15; AccountOwner -> xxxx; PaymentMeta -> com.plaid.client.response.TransactionsGetResponse$Transaction$PaymentMeta@42bc6c4b; Pending -> false; Date -> 2024-08-15; Amount -> 42.86; Category -> [Shops, Convenience Stores]; CategoryId -> 19015000; AccountId -> 9pYx7rDXvxFe73p1R9O9HxwoEXML5qI6KAd9p; PendingTransactionId -> v4ngJX6b8gtOVwa3BmOrUn3eJwA0eYI0ne9rd; UnofficialCurrencyCode -> null;
20240820-17:09:17.775: received MD+ txn: 0pYnyBjX1nF5XyE3zr5Qcy0a0xOXPwtXo4RAQ 20240815 Circle K -4286
20240820-17:09:17.775: Plaid: Transaction: Name -> Circle K; Location -> com.plaid.client.response.TransactionsGetResponse$Transaction$Location@58d4603e; TransactionCode -> null; MerchantName -> Circle K; TransactionType -> place; OriginalDescription -> null; PaymentChannel -> in store; IsoCurrencyCode -> USD; TransactionId -> 0pYnyBjX1nF5XyE3zr5qCvPw1X9xwKCvdqkRQ; AuthorizedDate -> 2024-08-15; AccountOwner -> xxxx; PaymentMeta -> com.plaid.client.response.TransactionsGetResponse$Transaction$PaymentMeta@4a7f2762; Pending -> true; Date -> 2024-08-15; Amount -> 66.29; Category -> [Shops, Convenience Stores]; CategoryId -> 19015000; AccountId -> 9pYx7rDXvxFe73p1R9O9HxwoEXML5qI6KAd9p; PendingTransactionId -> null; UnofficialCurrencyCode -> null;
20240820-17:09:17.776: skipping pending MD+ txn: 0pYnyBjX1nF5XyE3zr5qCvPw1X9xwKCvdqkRQ 20240815 Circle K -6629
it took 0.021 seconds to eliminate 1 duplicates from 2 downloaded transactions
20240820-17:09:17.800: Online downloads (account: 'Citi Costco Visa', service: 'Moneydance+') finished...
it took 0.134 seconds to categorise and possibly auto-merge 0 non-duplicate transactions
*** Download was successful
*** Started same download again
20240820-17:09:37.569: Online downloads (account: 'Citi Costco Visa', service: 'Moneydance+') started...
-----------------------------------------------------
JVM - Maximum memory possible: 14.4 GB
JVM - Total memory allocated: 0.8 GB (used 0.3 GB / free 0.5 GB)
-----------------------------------------------------
*** Hung for 90 seconds, nothing else in logs at all
*** Chose Quit menu....
20240820-17:11:22.758: Setting size of window dialog1 to location (812, 451) and size (424 x 250) on display Display 2 with bounds java.awt.Rectangle[x=0,y=0,width=2048,height=1152]
20240820-17:11:23.013: Beginning shutdown process
20240820-17:11:23.024: JVM status: cores: 8, maxmem: 14.41G, allocated: 813.69M, used: 341.29M, free: 472.41M
20240820-17:11:23.028: waiting for background tasks to complete...
*** Forced Quit