Reauthorizing One Step Update not working

cm_blk

I am using Quicken for Windows, R62.16.

I had message "CC-901 Your bank is requesting that you reauthorize your account. Click Reauthorize" for my Citibank card accounts.

After clicking the "Reauthorize" button and entering signon credentials on the web, I get the message in the web browser that my accounts were authorized successfully. The quicken window times-out and the online connection doesn't get enabled for the account that I was trying to re-authorize.

I was able to do one step updates on the second card after doing the re-authorization.

After trying to re-establish the online connection to the first card, the second card now shows the message "CC-506 Quicken is unable to update your account. This may be because the account was closed, or its nickname was changed." The first card is still not connected online.

I turned off firewalls and am not using a VPN. The issue seems to be that the Intuit web authorization to Citibank is working but Quicken is not getting the message that the authorization was successful.

Transaction downloads were working through April 10. Now I can't get any Citibank transactions to download.

Does anyone have any suggestions for reestablishing online access?

Quicken Anja

Hello @cm_blk,

We appreciate you reaching out regarding this issue.

Upon reviewing your account, we do not see any internal errors occurring; however, since you are currently receiving a CC-506 error in-product, we advise reviewing and following the error-specific troubleshooting instructions found in this support article.

Let us know how it goes!

cm_blk

Hi Anja,

I did the authorization step again on the account that doesn't return to Quicken after authorizing through Citibank. That fixed the CC-506 error on the second account. When troubleshooting with support earlier, I didn't check the second account to be available to Quicken on the Citibank page.

I am continuing to get the successful authorization message from Citibank web, but Quicken still doesn't recognize that the authorization was successful so Quicken doesn't register the reauthorization.

I am still unable to download transactions from my main credit card.

It looks like Citibank is authorizing access to Quicken but Quicken doesn't realize that access was granted, because the dialog box in Quicken continues to time-out.

cm_blk

I am getting the same error as this post:

Reauthorizing One Step Update not working — Quicken

I tried clearing out the general information on the account that won't connect. That didn't fix the issue. When I get time, I'll clear out the other two accounts from that Citi login. One of the accounts is closed and it looks like Quicken lost an old record from before 2016 as it now has a balance.

Quicken Anja

@cm_blk this is now a part of a known issue that has been escalated, though we do not have an ETA on resolution at this time.

Please refer to this thread here, as this issue is part of a broader issue that is occurring across multiple financial institutions. You can also submit your log files if you wish to contribute to the investigation via Help > Report a problem.

Thank you!
(CBT-658)

cm_blk

Thanks! Quicken has been pretty reliable recently. This is one of the few issues I've had recently, although this one does substantially impair use of the product.

When I initially did the "Report a problem…" I got the message that Quicken can't send the log files to support because it exceeded 10 files. Then the dialog box goes away, and I have to re-enter my problem description. The "Report a problem" checks 11 files by default. I'll randomly pick one file to not send. This seems like a bug with the bug reporting system.

My other issue is that I still lose past transactions randomly, although it is very rare now. I wonder if Quicken could write to a change log and use a two-phase commit. Perhaps Quicken could migrate from a file system to a lightweight database. I now have an inactive account that doesn't have a zero balance. It seems like current updates to the Quicken file can corrupt old transactions that aren't being updated.