Hi
Because this trigger operates inplay, I think you will get a number of selections meeting the conditions in a very short space of time. Also as you point out, the same selection might meet the conditions twice or more. As the trigger stands, it checks the conditions every second, but I think this is not fast enough. You can try reducing the time of the Execute no more often value, thereby increasing the checking frequency. The overall rate of checking is dependent on your market refresh rate.
Another method for improving speed of "No more often than" is to change it for "Specific number of times" and set it to a high number e.g. 50000. The trigger will repeat at market refresh rate for the number of times specified.
Additionally, the two triggers; remember and back require at least 2 refreshes for both to complete, so effectively the time needed to react to all the conditions is doubled.
mcbee’s suggestion of redesigning it to a single trigger will definitely improve the performance of the trigger.
I would suggest trying something like:
First Matching Selection
Conditions:
Selection’s Back Price is equal or less than 2.00
and any other selections trigger expression minbp_3 is equal or less than 2.00 (mcbee)
and Trigger Expression matching_number is equal to 2
and Trigger Expression match_index is equal to 2
or
Last Matching Selection
Conditions:
Selection’s Back Price is equal or less than 2.00
and any other selections trigger expression minbp_3 is equal or less than 2.00 (mcbee)
and Trigger Expression matching_number is equal to 2