Keep walking... ehem... trying...

Dashboard EAX

If all are of the same broker, you can try to copy the historical data from a working terminal to a non working one.... have you already tried this? The ForceLoadHistoricalData is not always as confident as one would expect.. you can also try the ...

Dashboard EAX

I'm not sure if I got you here.. Do you mean that it started OK after 10 tries?

Dashboard EAX

This is typically related to missing (historical) data or history in update state, but let's see... perhaps your suffix is not being properly detected... Can you confirm if do you see a message like any of these at EA start? > DBMASMEAX007a3 ...

Dashboard EAX

I see that you are following the "Troubleshooting" section in first post, that's a good place to start.. About that error, you can try posting the complete error description instead of a trimmed part of it...

Dashboard EAX

What a coincidence... two of the same kind published in the very same day.. LOL

Dashboard EAX

Yes, this one needs to be attached to open charts. To make this "easier", one can use the <Open all selected symbol's chart(s)> button ([~] header) after setting and defining a template for it (or use BDM). Before going to a dash version, I think ...

Dashboard EAX

I still have to do a proper evaluation (that I'll do as soon as I find the time to do so), BTW, at first glance this could be a good addition...

Dashboard EAX

I found (and fixed already) a bug in "Reset EAX on [...] session [...] start [...]" implementation that was generating that flood. DBMASMEAX007a3.bundle3 (20161023): rev.update.012.2 ~ Hold filter: + Scope: hold «bars,period» since last open order ...

Dashboard EAX

You probably have some filter/trigger hidden and enabled at the same time ... Try to walk through triggers/filters preferences to see if that's the case....

Dashboard EAX

You're still using an outdated revision update... and if you had done your homework, you'll notice that in that scenario and that revison update, you'll also need to activate the Close ANY feature .... (the latest revision update (201610141356) ...

Dashboard EAX

Sadly this didn't shed more light on your issue... Do you have by chance the log of the Experts tab between 13:47 and 15:12 of that day? The Experts log is way more useful than the Journal one for such cases... OTOH, I was thinking on your time ...

Dashboard EAX

So your VPS time is the very same of your broker's... thus sessions and terminal times are in the very same page as well. I think I can trust that your VPS clock is correctly synced and that I don't need an screenshot showing the EAX clock alongside ...

Dashboard EAX

I meant all your sessions related settings....

Dashboard EAX

By reading your previous posts, It seems that you are mistaking "bugs" with "not working the way you think it should", and these are two very different things. By the way, in the latest update I made some changes in the exit/close mechanism to try ...

Dashboard EAX

Hey allanatnz, what are your sessions settings and your time offset to your broker's server? (keep in mind that session times are local whilst terminal ones are from broker)

Dashboard EAX

Ops, that "Add trades after x bars" is not ready yet, It seems that I forgot to remove it input in the latest update (you'll find that there's no "hold bars,period since last open order" [H] scope yet)... (kind of busy sorting out issues/bugs) I ...

Dashboard EAX

Finally, after almost 2 full days of trying, I managed to upload a bug-fix update... DBMASMEAX007a3.update11 (201610141356): ~ Attempt to have a better integration between close/exit scopes. !! Fixed? ...

Dashboard EAX

I made some changes there from 007a2 to 007a3, and in last update I have added an option to Bias section to choose the arrow to be new/ancient (default to ancient). I'll probably end up removing the "new" behavior... it was an attempt to improve the ...

Dashboard EAX