nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

One Step Update fails for Citibank with CC-501 unknown error

Suew5929

I have been receiving this error when trying the One Step Update for my Citibank accounts (3). This has been happening since early last week, and I was hoping it would resolve itself. I have checked that Quicken is authorized as a third-party app and that authorization does not expire until September 2027. Currently using Classic Deluxe R69.53, build 27.1.69.53, Windows 11 Home.

Thanks for the assistance.

Sue Welborn

Find more posts tagged with

One Step Update

Accepted answers

Dan13

What I found recently from this CC-501 issue I had with my Bank of America / Merrill Lynch accounts, after about 3 - 4 days of not being able to connect, I "deactivated" my connections and "Reconnected". This cured my problem.

All comments

Quicken Levetta

Hello @Suew5929,

The response you received is Quicken's standard explanation for a CC-501, or “It’s not your fault,” error. Since yours has persisted for more than a week, though, I wouldn't just keep waiting.

Quicken’s current support guidance states that CC-501 generally indicates a connectivity problem between Quicken and the financial institution and that if it persists beyond 24 hours, Quicken Support should review the connection logs. It also specifically says not to deactivate/reactivate the accounts as a troubleshooting step.

Thank you. Hope this helps!

Marc Albert

I'm having the same problem.

Quicken Levetta

Thank you for reporting this issue. Please follow the steps that I provided in the previous post.

https://community.quicken.com/discussion/comment/20579972#Comment_20579972

Thank you!

Michael Farley

Same problem here. Quicken Premier Windows, latest version. Will send logs later today.

Dan13

Suew5929

I walked through the deactivate/reconnect process with support and my problem is resolved. Thanks!