Bluetooth buffer question -- tracking down an issue..

Probably one for @Gordon, but please chime in if others have help - I'm trying to track down an issue with a couple of my designs. After some long-ish period of time (many hours or days) of not being connected, my sensor designs 'crap out' and need to be reset and reloaded with js code.

I'm doing something probably bad which is just to keep writing to Bluetooth (Bluetooth.println()) without putting it into a NRF.on(){} construct. In other words, it is trying to output to Bluetooth when not connected. I'm going to guess that not only is this not a good practice, but it may be filling up some buffer to the point of producing the 'crap out' behavior.

I'll try putting it into the appropriate NRF.on and putting some test time on it, but if you could let me know if this is indeed an issue it would help me feel like I'm on the right track to getting the sensor more reliable.

Thanks!