Something a little more positive now:
Hi Mike, I am sorry again that you’re affected by this issue. We have reported this to our Engineering Team and we’re adding your ticket to the report.
The Team is now working on this issue and I hope that a solution will be available soon.
We do not have an ETA on when this will get fixed, but please keep your app up to date as the fix will be released through the future versions of the app.
I will be closing the ticket. But we will try to message you if we get an update about the issue or to check the status of the issue on your end even if the ticket is closed.
But if you have other questions/concerns, please do let us know anytime.
I also notice that the app seems to have been updated since I last added the problem account. I don't know if this is co-incidence.. it probably is. The version I'm running now is 4.2101.0, whereas the version that was giving me the problems was 4.2048.4
(and I'm assuming these are version numbers!)
I might reload the second account and see how it goes.
M