Dear JForex support,

This submission is in reference to an earlier support request I sent via email:
[~LHL-535103]: Problems with JForex standalone API 2.7.3

In the above support request I reported an issue with accessing order history, namely that trying to obtain a list of historic (closed/deleted) orders via the sync query method history.getOrdersHistory() frequently hangs (never returns).

I got a suggestion to try async reading of orders via history.readOrdersHistory() and was referred to the wiki page:
https://www.dukascopy.com/wiki/#Order_history/Asynchronous_retrieval

I have implemented the method outlined in this page. It does not solve the problem of request hanging. Most of the time it works as expected, but on some occasions (f.ex now, as I'm writing this) it still is unable to load historical order data. None of the instruments for which the async requests have been sent completes (LoadingProgressListener's loadingFinished() does not get called). I've been waiting for about half an hour now, normally it takes just a few seconds. This is on a permanent demo account with a very moderate amount of orders (a few tens of tickets over the last few weeks).

I would be grateful for any assistance, and I'm more than happy to supply any further information you should need.

Thank you in advance!

Dear JForex support,

I have just noticed that JForex-SDK has a new release 2.7.4 with a related fix in the changelog. I have updated my platform (from 2.7.3) and now the historical order download worked immediately. I don't know if this is only out of pure luck now (it used to work before, too, but at times suffered the hangs I was writing about) or something fundamental has changed about the query implementation in 2.7.4 (well, it says 'refactored' in the changelog, which - to me at least - does not imply any fundamental operational changes...). The fact that I was having problems for at least an hour long before the upgrade, and that it worked flawlessly right after the upgrade, makes me think the new version had an immediate effect, but without deep knowledge about the platform internals I cannot be 100% sure.

Anyway, I'll keep using it as is now, and report if any related problem persists.

Thank you for your time