Connection to CapEd Credit Union Consistently Fails, Support not helpful

emclusk

After several days of troubleshooting—including online guides, chatting with support, and a phone call—I am ready to abandon Quicken for Mac. The program no longer connects to my credit union, despite no changes to my setup. I have a secure Ethernet connection and no viruses. As an informed user, I was prepared when seeking help, but support has proven unhelpful. After dedicating over a week and many hours to reconnecting, Quicken for Mac still fails to update my credit union transactions. Support confirms that there are no issues with the credit union, and alternative programs like Banktivity and Empower—Personal Capital update transactions seamlessly. The data file parameter is as Quicken prescribes: my data file is located in /Users/[username]/Library/Application Support/Quicken/Documents.

All support does is run me through steps that are now too familiar and unsuccessful, leaving me where I started in trying to have Quicken connect to my credit union. I even asked for a refund, even though I am outside the “window” — “policy” — to refund a program that is utterly useless with months remaining that I paid for. I have been happy with Quicken for decades, but abruptly, since over a week ago, it has been different. Quicken seems unwilling to take responsibility for errors on their side, evidenced by refusals to escalate the issue during the last phone call, which puts front-line employees in an awful situation to just repeat the scripting; this, too, encourages looking for alternative programs. 

This issue, along with falling behind on things like automatic downloading of Apple Card transactions (which Banktivity now does), has this long-time loyal customer searching for alternatives.

emclusk

Later today, disconnecting and reconnecting all related accounts cleared this up. However, that's for today/this evening. The same thing happened two days ago and the problem returned. So we'll see….

Quicken Anja

Hello @emclusk,

We're glad to hear that you were able to clear up the issue and appreciate you updating your post to let us know. If the issue does return again, please don't hesitate to reach back out.

Thank you!