The TTL or time to live value is set to 60 seconds in all the published responses. To the best of my knowledge this is a “reserved-for-future-expansion” thing and is not used right now.
The stream should be continuously broadcasting (including keep-alives every 9 seconds) but it does die from time to time. There are three variables, the core, the cloud and the browser and generally speaking it is the browser that fails for me, but it is sometimes hard to know. You can use
curl to log events to a file on the command line on a PC too.
You can remove the connect button and just always connect to the stream when the html page loads. That would give you the best chance of restarting, but it makes debugging harder.
If you are worried about missed events, you should consider Spark.variables instead. With Spark.publish like in this tutorial, you get push-type behavior, but with Spark.variables it would pull-type behavior. Both are good but they just have different uses.
I am note sure what you mean by:[quote=“mwdll, post:47, topic:3469”]
It also doesn’t seem to be published, so I can’t leverage it in some downstream system.
So if you are having a specific problem, let me know and I will try to help.