Trade is disabled (133) error with binary options EA's that used to work fine in the past...

[safv6]

Hi fellow fxDreema users,

I've made quite a few binary options EA's with fxDreema in the past with no problems, but now I'm trying to make another one and all of a sudden I can't get it to trade and I keep getting this error "New trade error: Trade is disabled (133)".
I can trade manually and my old fxDreema EA's still trade fine with the same Buy Now block settings, on the same symbol and with the same broker (GDMFX). Weird, right? But it get's even weirder:
So I took my old fxDreema EA that still trades fine and I imported the mq4 file into fxDreema (I love that feature by the way), but when I do that and generate a new mq4 file right from the imported project that traded just fine, the newly generated mq4 file will again not trade!

Here's an example of the Buy Now block that works in my old EA's, but doesn't work in a new one. Looks fine, right?: https://fxdreema.com/shared/Qz2H9VFBc

I feel like I've tried everything. Thoughts anyone?

[fxDreema]

Not even a single trade? I remember such problems when I was adding this ability to trade on BO brokers back then. Can you really say for sure that 1 EA works fine every time while the other EA doesn't work and always gives you that error? Because I am thinking that it might be some temporary problem on the server.

[safv6]

I'd like to rephrase my question in a way that may be a bit more clear if that's ok:
The example EA below should be suited to make binary options bets, right? In the past it worked fine, but now every broker I try it on returns this error: "Trade is disabled (133)". I've tried goMarkets, GDMFX and a bunch of others. All brokers return the same error. My old fxDreema EA's that trade the same size and expiry and everything, with the same "Buy now" block settings all work fine (unless I generate a new mq4 file for the old project; this newly generated version of my old working EA will not work either).

Simple binary option EA example: https://fxdreema.com/shared/Qz2H9VFBc

Am I doing something wrong here, or is there something wrong with the OrderSend syntax for binary options in fxDreema nowadays? It should look something like this, right?:
" OrderSend(Symbol(),OP_BUY,Lots, Bid,3,0,0,"BO exp:60") "
Maybe the "BO exp:60" comment is not coming through as it should for some reason? (I'm just guessing here)

Any help would be very much appreciated.
Thanks in advance guys!

[safv6]

@fxdreema Hi Radoslav, I was rephrasing my question while you sent your reply just now. I tried my EA project and this example test EA on multiple brokers. All return the same error. The old EA that uses the same buy now block settings works fine, BUT when I generate a new mq4 file in fxDreema after loading OR reimporting the old working EA, the newly generated EA will not work at all.

So my answer to your question is: Yes, I'm sure that one EA (the one that I generated with fxDreema in the past) works fine and any EA I generate now doesn't. Same Buy now settings, same symbol, same broker. I'm not ruling out that it's user error somehow, but I just can't imagine what I could be doing wrong. I mean you see the example EA there, it should be working, right?

Thanks again for your time.

[safv6]

@fxdreema @miro1360

Hi guys, I truly think that it has become impossible to make binary options EA's with fxDreema since a little while, maybe because of an update to fxDreema or something? It used to work, but I'm convinced it doesn't work anymore. Not on any broker, not for anyone who'd try.

I've tried everything, I've read every thread on binary options on this forum as well as everything there is to find on error 133 using Google before I started this thread 3 days ago. Maybe it's the "BO exp:" comment that's not properly added to the OrderSend line anymore, or maybe it's something else entirely, but again, I really think something broke. Either that, or it's user error somehow, but I really really doubt it.

I'm stuck here guys! And I'm sure I'm not the only one.

I'm really hoping for your support on this one!

Best regards

[safv6]

@fxDreema
I've been a paying subscriber for over 3 years now and I must say I am really disappointed by the lack of support. I'm not saying it's your responsibility to reply or to address every issue, I'm just saying I didn't expect to get no support whatsoever. I am now using a custom MQL4 code block to bypass the issue.
I do appreciate the awesome software, just didn't expect to be alone on this one.

[FXFun]

I just got error: Trade is disabled (133)

No trades are taken at all.

The EA works perfectly on 4 other accounts accross 2 different brokers.

I asked my friend to check with the broker if there is any problem with them.

Sure enough, his KYC docs were first approved and money deposited to the MT4 account.

But, then the broker thought they needed cleaner photos or something so his account was dissabled, while waiting for new docs and new approval.

So I am happy that it wasn't a problem with the EA, as it shouldn't be, having worked fine else where.

I am waiting for his docs to be approved and everything is going to be fine.

THE ERROR SEEMS TO BE A BROKER IMPOSED LIMITATION.

Perhaps for other reasons as well, besides what was mentioned above.

BTW, this EA of mine that my friends asked me to run on their accounts, made me 500% in 9 days.

Deposited $500 and 9 days later had over 2500.

Withdrew 1500 and left 1000 on the account. (300% safe in my pocket)

The 1000 grew again to 1700 in 2 days. (today), Exciting.

Basically, it doubles the account every 4th day, with risky settings.
Or doubles every month or two with very safe settings. (7.5% Drawdown).

This is wild. Thanks to FXDreema for making it easy to program my algorithms!

[l'andorrà]

Let me guess! You are offering your EA's service for a price!

[VHV-Profit-Masters]

@safv6 Si usas un sistema de copy trading como el Mt2 puede ser que funcione.... hace algun tiempo yo lo use con un ea hecho en fxdreema desde una cuenta demo mt4 hacia poket options y tambien a IQ options