Re: Another One Step Update Error - TD Ameritrade (Schwab)

On Wed, 6 Sep 2023 19:02:29 -0700 (PDT), John Pollard
<[email protected]> wrote:

>On Wednesday, September 6, 2023 at 12:56:39?PM UTC-5, John Pollard wrote:
>
>> The last resort I can think of is to 
>> Restore the most recent backup from 
>> a QDF file that did not experience the problem.
>
>Tonight (09-06-23) @ 20:08 CDT time I did a One Step Update.
>I have checking, savings and investment accounts at Schwab -
>plus accounts with multiple other financial institutions, including 
>BofA, Discover, Chase, American Express, Vanguard and Fidelity.
>
>My OSU hung and I finally used Task Manager to kill Quicken.
>
>The Schwab updates did not complete; the others did - 
>it appears the Schwab update was what was preventing 
>the OSU from completing.
>
>I had done an OSU earlier today (at around 13:00 CDT) and 
>everything seemed to work ok. The OSU completed on its 
>own; the accounts that had activity available for download 
>(including Schwab) received their expected transactions.
>
>So when I responded in this discussion earlier today, it did not 
>dawn on me that there could be a problem with Schwab. But after 
>my experience tonight, I'm thinking there is something going on
>with Schwab. 

It occurred to me that that might be the problem.


>[Note: I have had no "conversions" of non-Schwab accounts to 
>Schwab accounts (nor created ANY "new Schwab accounts) for 
>many months, so today's issue does not appear to be related to 
>transferring holdings to Schwab. 
>Or creating ANY new Schwab accounts for downloading.]
>
>Sometimes when OSU hangs, and Quicken must be aborted; it's 
>just one financial institution that is causing the problem.
>In those instances, it is may be possible to use "Update Now" 
>(or "Update Transactions") to update the non-problem financial 
>institutions individually - while waiting for the problem financial 
>institution's problem to get fixed.
>
>I don't know whether that will help in your situation, 
>but it may be worth a try.


Yes, I'll do that. I think I'll wait with Schwab until next week., and
hope that if they are having a problem it will be fixed by then.


>[My everyday Quicken release is R50.16 which is the release 
>I referenced for all my earlier posts in this discussion.
>Tonight I also tested an OSU with R51.12; and it did not exhibit 
>the same problem. My OSU completed without a hitch.
>Since I don't try to keep my test file up to date, so I can't be 
>certain that everything downloaded - but the fact that Quicken 
>did not hang is interesting to me.]


I'm running 52.19

>Sorry I'm not up to digging any further into this at the moment. 


Understood. You've already been very helpful, and I thank you again.

>You may want to monitor the Quicken Community (as I will) to 
>see if there are any others having the problem, and to see 
>whether there is any acknowledgement from Quicken.

I've never been there before , but perhaps I will. If you see anything
there, please let me know.