Forex Retracer (GoMarkets) Diskusia

Is this the performance of the famous 3000$ EA?😲

Oh well, not too much I can do about it. It was doing OK but the GBPCHF and EURCHF trades yesterday went horribly wrong. We'll see what happens in the weeks to come...

good catch but it seems there are two EAs running on this account ... so it's not the full representation of the scalper ea

no there was only Scalper BigCat on this account without any other EAs.
the developer (Noordeen) gave me a different currency basket than the one he uses for his demo account.
I've noticed just now there were quite a few errors with BigCat on my GoMarkets account when I check on my VPS
there was a lot of 'trade context is busy' errors and BigCat were unable to close a few of the trades.
not sure if that's the cause of the loss but Noordeen said he's going to look into it.
we'll see what he says

He'll get it under control for you. He's been very helpful with me so far with BIGcat and I haven't had any of the big losses you've had. Even your -27 pip trade a few days ago is very strange.. pry due to your errors..

from the Experts/File Journy:
 
there were 2 big losers - #532###1 (buy on GBPCHF) and #532###3 (buy on EURCHF).
 
We don't see anything wrong for EURCHF trade besides big slippage on entry
(4.8 points, so entry was made at 1.44475 instead of 1.44523).

There were several 'Trade context busy' errors on the GBPCHF trade near 75 minutes
after entry (trade was closed 35 minutes after those errors). We don't see any trade
activity in the logs on other pairs at that time.
 trade context busy' errors may be due to bad execution (dealer holding request).
 
From the Experts/Log:
 

What we see in logs is that there is TP trailing - take profit is updated if price
goes against trade. One of these TP updates encountered 'trade context busy' errors
due to order modification on another pair. However TP updates were done successfully
several times later. Finally order was closed by TP so as far as we can say all was ok.
 
We have summed up a conclusion based on the following three points:
 
1)Since you have not ran any other EA when 'Trade Context is busy' error showed up.

2) Big slippage on EURCHF was negative (buy order opened at lower price.
 
3) TP updates interval is quite big (tens of minutes).
 
The First and third points shows that there has been Broker Latency from your VPS, and we advise that you run the BigCat from your own home computer and not from a VPS to avoid such Latency generated errors in the Future.
 
The Second point however shows a Dealer error, and you may need to contact GoMarkets regarding the huge slippage in BigCat Order.
 
Please Contact GoMarkets on the Dealer error.
 
Hope all makes sense.

<a href='https://www.myfxbook.com/files/nbakir/DetailedStatement.htm' target='_blank'>DetailedStatement.htm</a>



Attached is the detailed statement for the Demo Gomarkets account for the same period the two GbpCad and EurChf trades were taken on your Live account.

The Demo account has been setup with a slightly bigger currency Basket but with the same exact settings as yours, and is showing 20% Gain in 3 days.

-$650 seems like a lot, but it'll recover.. I've lost thousands trying other ea's as I'm sure you have Jimmy, so lets put our faith in mr. Noor and let his system prove it's abilities :D. I'm still running it with good results. Everybody can see my stats and identify bigcat trades with text bubble at far right of trade history.


~~~~~ Andrew.

I think over the last 2 weeks BigCat has proved its worth. It has recovered from -20% to a positive balance.
Everything seems to be working well now. :)

For sure Jimmy. I hope to replicate your results soon (accept for the drawdown of course) because I'm going to GoMarkets next week! Can't wait. I think this EA is a winner. Noor is getting more clients now and all are on fxbook proving this ea's power ;) Happy for ya,

Cheers,

Andrew.

Just for anyone who is viewing this system. BigCat performed quite well after the first big loss on Mar 18, but then the same thing happened again on Apr 06. On both days there were a lot of errors from the server, 'trade context is busy', 'unable to set S/L or T/P', 'unable to open order', etc, etc. I have already changed the VPS to one based in Australia but it still happened.

I am not sure what the problem is but it seems to be with the broker (although I can't quite explain why the same big loss didn't happen to the developer's GoMarkets account). Anyway, I am switching to AxisODL now so this BigCat won't be run on this account any more.

regards,
Jimmy

Jimmy, If you wish to never see any errors on your AxisOdl, just drop the hedging strategy.

most GoMarkets Errors were generated out of over trading, This is a problem comming from our side, eventhough a client can simply avoid it by lowering the lot size used.

BigCat version 2 will not allow this to happen.

Version2 will be released in 60 days though, we still need to see what other customers say about BigCat and gather all there reports so that there wont be that many version release. Just get everything done in version2

So I shouldn't get many errors noor if I'm running same pairs as you on gomarkets? So far, my account is mirroring yours quite nicely :D.