I GIVE UP

Discussion in 'Trading' started by hilmy83, Aug 29, 2023.

Thread Status:
Not open for further replies.
  1. hilmy83

    hilmy83

    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...

    upload_2023-8-29_12-27-24.png

    Wife's account with pretty much, no issues.

    upload_2023-8-29_12-27-42.png
     
  2. hilmy83

    hilmy83

    I have to retrace every step and try to figure out why the hell it left that long order open. But why would it not work on my platofrm and it does hers?

    This could've went the wrong way and I would probably break some shit
     
  3. destriero

    destriero


    Obv we can't help you but aren't you coding to trade the bigs when size exceeds nine lots? Or do you scale on the cover?
     
  4. hilmy83

    hilmy83

    Yes, when it gets to 10 micros, it would just transition to emini.

    I don't scale at all. It's all in and out, but of course market sometimes break those lots out when they execute.

    It's a simple stop and reverse logic. When price moves fast, the algo should work still. What annoys me is we use the same algo, on two diff vps from the same company. Is the vps effed up or something?
     
    destriero likes this.
  5. TrAndy2022

    TrAndy2022

    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.
     
  6. destriero

    destriero


    oic it was a short to cover (10 lot).
     
    hilmy83 likes this.
  7. rb7

    rb7

    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.
     
  8. Overnight

    Overnight

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

    rb7

    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.
     
    nbbo and murray t turtle like this.
  10. 2rosy

    2rosy

    i assume you're tracking orders and positions incorrectly. probably this is written without staying aware of acknowledgements
     
    #10     Aug 29, 2023
Thread Status:
Not open for further replies.