The cloud headless client warns on slow startup and reconnects when a session goes quiet.
What's wrong with this entry?
While the cloud container is still provisioning, a timer warns once if anything is already queued to send. After each send, a watchdog reconnects the stream if the cloud session goes quiet, using a longer timeout while the session is compacting its history.
- Both timers increment a
watchdog_firescount in the record written at end of run. - Reporting presence and setting a session title are skipped when the session is in essential-traffic-only mode.
Still waiting for the cloud session to start; what you sent will be delivered when it is ready.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.