I GIVE UP

[d08]

That is with full algo trading, it can happen all the time of a sudden. That is why any full automation needs to be babysitted. With any retail software and retail coding you cannot get out of this I am pretty sure. That is why I only trade manually. I have anytime full control of any orders.

There really can be a lot of issues why this can happen. I cannot write a book here nor I am able to list all kind of possible errors when it comes to automation.

Sorry, but you cannot leave the trading desk when trading. That is sad but true.

Babysitting isn't always required but it takes a very long time to work out all the possible issues. It takes years because most of the problems are not obvious at first. But you're right that some commercial piece of software is unlikely to handle all your nuances.

 

[Pica550]

I had similar issue in my code that’s why I was looking for someone to help me add the time element. But instead of complicate things I have decided to just enter everything mkt, I have only tested for the past 2 days the slippage wasn’t bad.

I checked the MT5 terminal to see a different view of the trades, and found the issue:

View attachment 322100

Basically the sequnce should be this:

buy or sell stop entry
set limit target
cancel other order
set reverse order

So the time difference betwen 4 (3+1) contracts entry and the first target hit (just on 3) is like 100ms.

It seems like today, it was so quick that it only had time to set a buy limit on 3 lots instead of 4, ending up screwing over the whole algo sequence leaving a naked reverse order.

I think the best way to fix this is just have a TIMER sequence initiated anytime a LIMIT order is filled. This could cause some losses because sometimes the market would reverse right off the level and only execute some lots. But it's much better than to have a naked order left open like today.

Partial lots has been the bane of my algo existence

 

[d08]

Full auto trading is like full auto driving.

Still not there yet.

Nearly all of it is due to new market regulations or broker changes. The code part can be done and has been for a while.

 

[SunTrader]

Nearly all of it is due to new market regulations or broker changes. The code part can be done and has been for a while.

Misunderstood what I am saying. Of course it is possible to code. But chit happens. And one needs to be there - IMO.

Seen it many times before... to others ... who knew what they were doing.

Connection goes down, even a blip can reset things and mess things. Just one of many problems that may need to be rectified by somewhere there.

It is why some brokers market the service to babysit your "baby".

 

[Drawdown Addict]

Misunderstood what I am saying. Of course it is possible to code. But chit happens. And one needs to be there - IMO.

Seen it many times before... to others ... who knew what they were doing.

Connection goes down, even a blip can reset things and mess things. Just one of many problems that may need to be rectified by somewhere there.

It is why some brokers market the service to babysit your "baby".

You start developing a serious algo when 80% of your code is about exceptions handling. Pretty much like any corporate solution. It is very easy to design a "happy path", but to cover every single path, that's another matter.

Triggering an order is something anyone can do. Acting when that order fails is something else.

Op's code is very amateur. A classic example of someone that went to fiver to code his algo.

 

[d08]

Misunderstood what I am saying. Of course it is possible to code. But chit happens. And one needs to be there - IMO.

Seen it many times before... to others ... who knew what they were doing.

Connection goes down, even a blip can reset things and mess things. Just one of many problems that may need to be rectified by somewhere there.

It is why some brokers market the service to babysit your "baby".

There are ways around some of these issues. For one, having critical orders rest with your broker if possible. Definitely using a VPS over a home internet/electrical connection. One really important factor is error handling, making sure that no problem whether unforeseen or not can cause lingering issues.

 

[SunTrader]

There are ways around some of these issues. For one, having critical orders rest with your broker if possible. Definitely using a VPS over a home internet/electrical connection. One really important factor is error handling, making sure that no problem whether unforeseen or not can cause lingering issues.

Some, not all. I'll let you know when I come across someone who, honestly, claims to retail auto- trade uninterrupted for years now.

Better yet, maybe you can save me some time and point me to such a person?

 

[d08]

Some, not all. I'll let you know when I come across someone who, honestly, claims to retail auto- trade uninterrupted for years now.

Better yet, maybe you can save me some time and point me to such a person?

That's obviously impossible. There are regulatory changes; brokers and data feeds update platforms and APIs and break backward compatibility etc. I've had about a week where I only checked in before/after market to see what happened. Few of the changes are problem fixes, most are feature additions/improvements.

 

[SunTrader]

That's obviously impossible. There are regulatory changes; brokers and data feeds update platforms and APIs and break backward compatibility etc. I've had about a week where I only checked in before/after market to see what happened. Few of the changes are problem fixes, most are feature additions/improvements.

That's my whole point. Auto-trading can be done ... over periods of time. Not sustainably though - without some human intervention.

 

[SimpleMeLike]

I don't understand how a simple fucking algo with simple rules can have intermittent issues.

Today I ran my algo as always. I just so happen to check the platfrom on my VPS, for no reason. Maybe it was intuition or some higher power made me check. But anyway, instead of the algo closing out the session as it should with modest profit, I saw that it left open an order that went my way for about $6k profit instead.

This could've easily went the other way because this order didn't have the proper stop in place like it should have based on the rules I have.

The funny thing is my wife who's also using the same algo, the execution worked.

I fucking give up man. I had issues on MT5, and this shit comes up on QT now. Is the platform so slow that it can't handle the orders I'm placing or is the logic broken??

This algo is pretty much vulnerable because of this bug. And the dev I used for this is pretty much MIA...

View attachment 322095

Wife's account with pretty much, no issues.

View attachment 322096

Hello hilmy83,

Keep on trading buddy. It is no big deal.

Nothing is perfect in trading.

And looking for perfect in trading is too much work.

Do not work hard in trading, just let the system run and check to make sure it exit the trade at about 3pm.

Over working in trading leads to losses.