I GIVE UP

[hilmy83]

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.

That's what I'm afraid of. I thought i could jsut let this run for the week and not worry about it. But I do work 9-5 and I just happen to be at home early and checked this.

I wish I could trade this manually but I can't becuase of the session and short time frame makes it impossible.

That's very bad.
You got lucky (in a sense!) that your position went on the right side.
That's the drawback of using a third party platform to automate trading.
On top of that, you're not the one who had developed it.

If your developer was good and if QT allows it, you should have a log of everything. But that won't necessarily show you why it failed.

You need to have alerts when things like this is happening (not sure if it can be done with QT).
I have many types of alert.
One of them is when discrepancies are discovered between what I should have vs what IB has. But nothing is perfect. Alerts have to be transmitted in a timely fashion.

QT has its own alert system i can use. I added a pnl alert via telegram. I can add all trades alert.. But that really doesn't help when i get an error message and I'm in middle of work lol. What am I to say, hey boss, sorry I gotta go I'm losing fucking loads of money right now

I thought you were up to only 4 micros? Seems you're up to 12 now?

1x ,1x, 1.5x, 1.5x 2x 2x sequence or something like that. It's all in the rules I have how to manage those reverses.

 

[Overnight]

That's what I'm afraid of. I thought i could jsut let this run for the week and not worry about it. But I do work 9-5 and I just happen to be at home early and checked this...

All things being equal, there is one variable you introduced, yes? You changed from the AMP version to the vanilla QT.

Are you and your wife using the same QT flavor/version? Still some investigative work to do methinks.

 

[Laissez Faire]

Don't give up, buddy.

You have a nice chunk of change now and it's been working fine until today.

Figure out what went wrong, solve it and take action to protect yourself from future occurrences.

Couldn't a simple auto-liquidate (maximum daily loss limit) be implemented as a fail safe?

 

[hilmy83]

All things being equal, there is one variable you introduced, yes? You changed from the AMP version to the vanilla QT.

Are you and your wife using the same QT flavor/version? Still some investigative work to do methinks.

We use the same AMP's version. I doubt it's that, but yea i need to look a the log and figure it out. But still, I need a damn dev

I seriously envy those that can code.

 

[hilmy83]

i assume you're tracking orders and positions incorrectly. probably this is written without staying aware of acknowledgements

I mean it's been running for few months, i've had multiple sesssions where i had orders broken up. But today, something happened...

 

[rb7]

Every piece of software has its own bugs.
A 100% bug free software is impossible.
We just need to get alerted as soon as shit happens and make the appropriate measures.
In your case, it's probably better to have an imperfect automated algo, prone to bug from time to time, than to not trade at all because you have a full time job.

Most likely, you'll find the bug and fix it.
Next time, you might get a new bug, different than this one.

Some bugs are happening very unfrequently, only under very specific conditions.
Those conditions might happen once a year, once every 2 years. You just need to be prepared when it happens, cause you can't avoid them.

There's positive in everything.
Today, yours was that you made money nonetheless...

If my experience can ease yours, I had a bug in my system, which was occurring once every 2-3 months. I was never able to find what was wrong until it happened again and generated a 10K$ loss. That was in last October (the day prior the CPI report). Yes I had alerts, but they never reached me (I fixed that bug also). I wish I had a 10K$ gain instead.

 

[murray t turtle]

Although nothing is perfect, not all automated system needs to be babysitted or monitored.
You can do as many errors trading manual vs trading automated.
Fat fingers (amongst other things) are usually not generated by automated algos.

%%
True;
@ least he caught the errors+ hers did not goof.
Knight capital had a $440 million trainwreck , so auto algos can trainwreck also.
But had a happy ending for the buyer of the trainwreck if i remember right+ usually do.
I dont mind making money off an error, but its labeled an error.

 

[TrAndy2022]

Better to stop now and when you have no time to trade fulltime. I heard from one guy who lost 100k in one day. When he came home he noticed it. And that was substantial money. So better to stop that earlier than be sorry later. I cannot say better words to that issue because it is that bad as it is. There can be always problems when it comes to full automation. I tried myself in the past and I can sing a song from that odysee.

 

[ironchef]

Maybe it is not an error. Maybe it is the result of a program logic that prevent it from closing because the logic -> profit.

Maybe you can capture that logic and start printing money.

Many new inventions (3M post-it, teflon...) came from errors or accidents.

 

[hilmy83]

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

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