Because TIME will never reach 1430000, and, it’s AND’ed  in the logic condition of the IF statement, the statement will never be TRUE, so no order will be executed.

Being a rookie means you have the greatest potential to learn and improve, exciting!. An expert may be bored of doing the same thing over and over again before something new comes along.

It takes 10% of the time to learn 90%  but,  90% of the time to learn the last 10%.

It maybe an idea to set the 143000 as a variable at the top of the code, since its used three times.

Using it as a variable allows you to change the time in all three places from one point,  if needed.

Also, if you type the variable name wrong, you will get the unknown variable error to warn you.

There’s a problem on the same line as before, but with the logic.

I think the three time conditions need to be overall enclosed in brackets for the OR operation to work correctly without affecting c1.

The lack of brackets is AND’ing the  c1 to the last time condition on one branch of the OR.

If not onmarket     and      (time = 143000  OR    (time > 143000 AND time[1] < 143000))     and   c1  then

I think what was happening was, when time = 143000, everything in the other  OR  branch was irrelevant, and a order was taken regardless of c1.

1 OR 0 = 1

The common factor between different ema setting would be 143000.

Not sure though what your  intensions are with the times.

1.   if time  = 143000 then other OR branch  ignored…
2.  if time > 143000(144500) then AND’ed to time[1] <143000 which will be 143000  @15m  and hence (1.)    1 AND 0 = 0

This was why order was taken regardless of C1 because of the AND’ing of c1 to the OR branch which never was needed @15m, and if an entry, it would be taken at 143000.

regards