@ScruffR - So do you think adding delays would correct or band aide an issue where it doesn't occur anymore? Is it by chance I had a race condition of some sort? I added this:
Serial.println("Reached debug step: x") delay(100);
Where x is just a 1 up number at different points. Prior to adding this it was occurring about every 2-4 hours between capturing an event. Since I added this to about 10 lines, it now has been 6 hours or so and hasn't occurred yet. This
Would adding a few delays here and there be a reasonable way to explain it? Not sure if I should let it go like this for a day in hopes I eventually catch something or if I should start taking a delay(100) away one at a time and see what delay had an impact. Maybe it's just the old phrase "a pot watched never boils" and I need to be more patient. The pieces of logic right before/after/around involve:
JsonParserGeneratorRK.h
PublishQueueAsyncRK.h
base64RK.h
Basically, taking an array of bytes, converting them to a base64, packaging it in a JSON object and then queuing that data to be published. Somewhere in the middle of this I do a Serial.println() and it is in mid stream of printing this out using serial print where PuTTY stops updating and SOS occurs.
The unusual or maybe surprising part to me is once the device reboots itself after the SOS x10 flashes, once it reconnects to the cloud, one of the first messages that hits the particle cloud even before the device vitals is reported is the queued up event from before the SOS event. I would of thought an SOS type error was a hard reset and all memory cleared.

For now, I just sprinkled in 10 different print lines and one up numbers with the delay() to try and figure out what's the last line that was executed before the SOS. Since the message was actually queued up to be published, I wonder if something is occurring after this. It just happens to be right in the middle of writing this to serial when the serial port freezes, I'm using PuTTY for serial monitor. Just thought I'd share a little more detail as I keep working through it incase you or someone has ideas to try.