Over a year ago, the OL-393-A error was reported. Numerous complaints had been lodged and comments shared. At one point, I went right to the President of Quicken about the issue. In the end, I was told the issue would be / was resolved.
Well, it has not been. But, there is a caveat. The error continues to show up with every One-Step Update that is done (and I perform one nearly every day). However, transactions are both uploaded and downloaded. So, while the error shows up at the end of every update, the transactions all go through in both directions.
Well, one might ask, what is the concern?
The concern is decensitizing users to errors. If there is no issue, Quicken needs to resolve the continuous population that there is an error. And if there is an error, Quicken needs to get to the bottom of it and resolve it once and for all. Ignoring the problem decensitizes users to error codes and reduces the responsiveness of reporting errors as well as the speed of error resolution. When an error shows up, it deserves attention and prompt attention at that.
Please fix this issue once and for all!