It sounds like 30 minutes just might be too long to wait on entry. We aren't even sure it is the same signal, it could be a completely different signal. Ideas?

One idea is to cut the time limit down to 1 minute (time value of 60) and 5 minutes (300) instead of 15 (900). Another option is to try large values (50, 100, 200, 400) for tick based calculations. I think that would require Build 200 with the best tick estimation :/ Do you mind testing some more or all of these settings? I appreciate your reports a lot, and I think this signal_count is our best candidate for making Phoenix more reliable on processing data.

I'm playing hokey and doing Phoenix stuff while code for cash runs through tests.