Upd:
Trigger0-> reset "wait after bet" timeout (waitbetdone_timeout)
(exec: 3*inplay_rate)
Trigger1(check trade conditions)->set "wait after bet" timeout (waitbetdone_timeout)
(exec: 3*inplay_rate)
Trigger2(trade if "wait after bet" timeout (waitbetdone_timeout) > 0)->cancel then back {unmatched rest}
(exec: 3*inplay_rate + waitbetdone_timeout)
Trigger3 log:
13:18:51 | Selection: Over 0.5 Goals, initial expr.: waitbetdone_timeout, intermediate: 55, final: 55. |
13:18:51 | Condition is: TRUE. valid for 1 selections: Over 0.5 Goals. |
13:18:51 | Selection: Over 0.5 Goals, initial expr.: back_price, intermediate: 1.78, final: 1.78. |
13:18:51 | Selection: Over 0.5 Goals, initial expr.: bet_size - back_matched, intermediate: 15-0.0000000, final: 15. |
13:18:51 | Going to BACK on 1 selections:
Over 0.5 Goals, $ 15,00 at 1.78; |
13:18:58 | Checking market "Soccer - Todays Fixtures / Sevilla C v CD Guadalcacin / First Half Goals 0.5". |
13:18:58 | Checking condition and Market's Betting Code is First Half Goals (Soccer) 0.5. |
So, Trigger3 gets the correct waitbetdone_timeout, intermediate == 55 but totally ignores it inside
"execute not often than 5 + waitbetdone_timeout" parameter - it starts next execution already in a 7 seconds(from log)
And yes, in case of action "set waitbetdone_timeout = {another_triggerconst_value}" it becomes even much more fun:
12:46:22 | Checking condition and Selection's Trigger Expression waitbetdone_timeout is greater than 0. |
12:46:22 | Selection: Over 0.5 Goals, initial expr.: waitbetdone_timeout, intermediate: 0_const_const_const, final: 0_const_const_const. |
12:46:22 | Selection: Under 0.5 Goals, initial expr.: waitbetdone_timeout, intermediate: 0_const_const_const, final: 0_const_const_const. |
12:46:22 | Condition is: FALSE. |