Problems with log 333

Viewing 11 posts - 1 through 11 (of 11 total)

Author

Posts
11/21/2023 at 1:54 PM #224041 quote

Mr.Mjau
Participant

New

Have been using log 333 for a long time and it’s working great, except one thing. I sometimes get this error

“Your trading system was stopped because it tried to place a stop order below the minium distance required by your broker.”

This stops the strategi and I have to restart it, so I always have to check if it’s still running.

Is there anyway to fix this?

11/21/2023 at 2:01 PM #224043 quote

GraHal
Participant

Master

Yes tick the box shown at the red line on attached.

What is Log 333 anyway??

Mr.Mjau thanked this post

Screenshot-2023-11-16-110026-1.png

11/21/2023 at 3:16 PM #224057 quote

PeterSt
Participant

Master

GraHal wrote:

Yes tick the box shown at the red line on attached.

I like some of those opportunism pills too !
🙂

GraHal thanked this post

11/21/2023 at 4:59 PM #224071 quote

Mr.Mjau
Participant

New

log 333 is

Trailing Stop starting from Stop Loss

You are the one that added it, don’t you remember 😉

So by just checking that box it will work fine from now on?

11/21/2023 at 5:13 PM #224075 quote

PeterSt
Participant

Master

Of course GraHal still knows. I know it too. Hahahaha.

GraHal wrote:

Link to above added as Log 333 here …

Snippet Link Library

11/21/2023 at 5:28 PM #224080 quote

PeterSt
Participant

Master

Mr.Mjau wrote:

So by just checking that box it will work fine from now on?

I don’t want to rain on anyone’s parade, but after by now 1000s of autotrades and 100+ failures like yours, Mr.Mjau, I have never seen this helping (and I always check that box).
Please notice : that checkbox helps for adjusting a too close to the price setting for pending orders. You can see it at work if you know what to watch for (I must have some videos from it somewhere). And problem is : that does not go wrong. Only if you had an open position and then the system is kicked out, it would be related (so tell us pls).
… But I only see this error occurring at the opening of a position, hence, the attempt to that (nothing opens and the system is kicked out).

For another topic and another day : I more and more start to see or feel that it is a plain PRT error, and not an IG thing. Why ? well, because the position never even opens, the mentioned price (-distance) never makes sense (like 100+ points for Nasdaq), and it occurs with systems with a Stop Loss command in them only. Regarding to this I also see a relation to that other checkbox (about the guaranteed stop we need to pay for), which is something which is arranged for in advance of the trade. I never ticked that one, but al least that literally relates to the Stop Loss command and how something needs to be registered at IG so the extra money can be charged.
It is all a bit of a long shot, but it still is definitely so that systems without a SL command in them, just never fail on this error (like not even once in a year of time and ~10 trades per day).

Mr.Mjau thanked this post

11/21/2023 at 6:59 PM #224090 quote

GraHal
Participant

Master

Mr.Mjau wrote:

don’t you remember 😉

HAHAHA … if you’d said Snippet Log 333 then I would have understood, maybe even remembered! 😉

I’ve been ticking that box for 2 or more years and I can’t remember the last time I had a Reject for ‘minimum distance’. I used to get loads of System stoppages before that box became an option.

It could be coincidence??

Mr.Mjau and PeterSt thanked this post

11/21/2023 at 7:11 PM #224092 quote

Mr.Mjau
Participant

New

xD

I will try with the box and get back here and post in a month or 2 when I have some data.

GraHal thanked this post

11/22/2023 at 12:47 PM #224128 quote

PeterSt
Participant

Master

GraHal wrote:

I’ve been ticking that box for 2 or more years and I can’t remember the last time I had a Reject for ‘minimum distance’.

Oh, but I can. 🙂 Shall I look for your more recent posts about this ? haha.

But … there is a difference indeed … As I told somewhere in between the lines, the whole IG department which tended to put the lot on (manual) hold, has vanished (from Amsterdam). Besides that, it sure is more quiet recently, so that nobody needs to put the lot on Manual. But there are still exceptions, like last week (see 2nd attachment).

And there is again more – see 3rd attachment. That one is new. It was developed in some kind of co-work with me (oh wow) and at predicted busy times PRT won’t kick out anything. Also observe the time in the 3rd attachment (Amsterdam time). I am not sure whether normally that would have implied a kick-out, but I think it does because of the triangle which surely does not show each day around that time.

Another new thing is implied by the 2nd attachment in combination with the 1st : although the message in the 1st tell that a system was stopped, in practice it is not always. See the end of the list of emails which is from last week, while the 1st attachment shows yesterday, the 21st. And nothing was kicked out. 🙂 🙂 Thus, such a situation indicates that something was wrong with this dreaded distance (which for the only thing applicable – the SL – is always way more than 4 in my case), but the system now keeps on running.

Something else is (OffTopic) that I think I so much complained about kicked out systems and how we can not find them back in the list of not running systems where they reappear randomly – twice actually because again when making the Stop sign green again – that they now asked me how to improve that ProOrder form for V13.
So yeah, slowly … 🙂

image_2023-11-22_121920321.png image_2023-11-22_122712482.png image_2023-11-22_122755024.png

11/22/2023 at 1:00 PM #224134 quote

GraHal
Participant

Master

Keep up the Good Work PeterSt – Thank You!

PeterSt thanked this post

02/14/2024 at 4:28 PM #228177 quote

Mr.Mjau
Participant

New

Ticked the box now for almost 3 months and everything is working fine now, 0 errors. GJ boys!

GraHal thanked this post
Author

Posts