As mentioned in the help files, reloadEFS can trigger "unexpected" behaviour".
One of them is that ALLBARS indication may never be received in real time and busy markets [see my previous post].
This can create serious problems [if one relies on ALLBARS to initiate studies, like I do], but is a simple bug to fix, because the problem is obvious: If first call/tick [after reload] is not on NEWBAR, the EFS engine fails to generate ALLBARS indications.
Please escalate the issue to your design team. It should be very easy to fix and a great help for us [your paying customers].
One of them is that ALLBARS indication may never be received in real time and busy markets [see my previous post].
This can create serious problems [if one relies on ALLBARS to initiate studies, like I do], but is a simple bug to fix, because the problem is obvious: If first call/tick [after reload] is not on NEWBAR, the EFS engine fails to generate ALLBARS indications.
Please escalate the issue to your design team. It should be very easy to fix and a great help for us [your paying customers].