Chase Bank - Error OL-294-A
Found at:
As with virtually every single OL-nnn error, this error was almost certainly a financial institution error.
The first thing users should do when they get OL-nnn (or CC-nnn) errors, is go to the Quicken Knowledge Base
Doing so in this case would have produced a description of the likely causes of an OL-294 with possible fixes/workarounds, and included the following final paragraph:
"If the issue is not resolved after following the steps above, you will need to contact your financial institution to resolve this issue. Quicken does not have access to the financial institution's servers to correct the problem. This may require you ask to speak with an online services specialist that handles transaction download issues at the financial institution. If your financial institution states they can't assist, an escalation with the financial institution may be necessary."
Armed with the information from the KB article, no one should have felt the necessity to bombard the Community with interminable repetitive "me too" posts. Instead, the appropriate actions were: contact Chase, then wait.
And it appears that waiting has paid off. This morning I received an email from Chase containing the following:
"We've sent an important communication to your Secure Message Center.
"The subject is: Action Required for Quicken or QuickBooks users
"Within 7 days of this notice, please sign in to Chase Online or J.P. Morgan Online as you normally would. For the best experience please use your desktop computer to do this."
After signing in to my Chase account, reading the Secure Message, and taking the required action; I successfully downloaded from Chase to Q2020 R26.17 and Q2020 R28.23 (not that the Quicken Release should matter).
Unless Chase has prematurely treated their problem as solved, I think other users should now be able to download to Chase without a problem.