43 Algos Stopped – Due to an Error!

Forums ProRealTime English forum ProRealTime platform support 43 Algos Stopped – Due to an Error!

Viewing 15 posts - 1 through 15 (of 20 total)
  • #245201

    Anybody else get this on Demo Account … ALL / 43 running Algos stopped (see image 1) with error message ‘Due to an Error’.

    Trades remained open as manual trades (see image 2).

     

    #245205
    JS
    #245206

    I got all my Systems started again no problem … all is ‘calm once again’ for now anyway!

    1 user thanked author for this post.
    #245207
    JS

    This is about a “live” system where I found out on Sunday evening that it had been stopped due to an “internal error”, but the position was still open…

    #245536

    Yes, I had this on two of my live Spread Betting accounts. There was an error on 24 March at 12:15 BST (UK). PRT and IG tell me they have fixed the problem. It left me in a mess as all of my positions were left open and unmanaged. They’re discussing reimbursement for the losses as I had many trades left open, unmanageable, and in the red. They would eventually have returned to profit if the code was still running.

    2 users thanked author for this post.
    #245537
    JS

    What bothers me the most is that PRT says nothing about this…

    This is ‘live trading’…

    How is it possible that positions remain open without any warning?

    Very concerning and unprofessional…

    1 user thanked author for this post.
    #245539

    positions were left open and unmanaged

    Wow, bad!, I sympathise.
    Which option did you have enabled in Settings, see attached.

     

    1 user thanked author for this post.
    #245937

    I have ‘Remain open’ selected. I prefer this because in the past I’ve accidentally stopped a system, and didn’t want my positions to close – but I’ll probably change it back to default now.

    My justification to PRT is that this setting is designed for cases like manual trade intervention or a system code failure. If the issue is a platform failure, then it’s completely out of my control, and I believe losses should be reimbursed on that basis.

    So far, support have been very professional and thorough, but we haven’t yet reached a final conclusion.

    1 user thanked author for this post.
    #247359

    I had the same thing this weekend again. All my algos stopped due an error, looks like there was some issue on PRTs side again. All of my positions were left open and unmanaged, which caused losses that should not have happened – but also missed gains as the algos needed restart and I wasnt able to get to a computer. Two times in two months – what is happening?

    1 user thanked author for this post.
    #247360

    All of my positions were left open

    Wow, bad!, I sympathise and empathise how you are feeling!
    Which option did you have enabled in Settings, see attached.

    #247362
    JS

    The same thing happened again this weekend with my son’s system: the system stopped due to an “error” (with no further explanation), and the position remained open despite the setting that positions should be closed automatically…

    2 users thanked author for this post.
    #247363

    I had the exact same error JS.

    Grahal: I have the setting on closed, as per default.

    2 users thanked author for this post.
    #247375

    I just had 24 Demo Algos Stopped about 2 minutes ago … about 20 due to ‘external event’ and the other 4 due ‘too many retires’.

    #247378

    Demo – 4 more Stopped, then a minute or so later another 3 stopped.
    I can see 7 more that are ‘Stopping’.

    #247395

    4 due ‘too many retires’.

    Hahaha

     

    1 user thanked author for this post.
Viewing 15 posts - 1 through 15 (of 20 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login