Share New Research 
Hi,
I'm seeing some strange behaviour on live deployments (both locally and on the terminal) - sometimes, some messages sent through Log will not show up. Changing them to Debug makes them appear. They are timestamped and so should not be deemed as identical to any other messages sent prior.
As such, I'm wondering how exactly Log and Debug differ in a live deployment. I've scoured the source code and documentation and cannot find any immediate differences. They both get enqueued onto the same concurrent queue - although the packet type itself is different. In the documentation, one seems to be sent to the console and the other to a log file.
Can anyone shed any light on this, and perhaps come up with a theory for why my message doesn't appear as a Log but appears when sent as Debug?
Jared Broad
Can you please post an example?
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
Douglas Stridsberg
Turns out this is due to me pushing more than 500 messages into the queue before 250 ms has elapsed. Sometimes - especially at algo startup - someone might want to send a lot of messages through almost instantaneously. Is there a good reason to keep this limit? Git blame tells me this line is all the way from 4 years ago at the initial commit.
Link Liang
Hi Douglas,
We have received your Github issue. Thanks for your support!
Douglas Stridsberg
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
To unlock posting to the community forums please complete at least 30% of Boot Camp.
You can continue your Boot Camp training progress from the terminal. We hope to see you in the community soon!