What the app does with its telemetry when it closes: whatever the process
accumulated and has not delivered is sent before the process is gone (owner
decision, 2026-10-24: closing a simulated app is closing the app — pending
telemetry goes out, then the connections close). The platform's entries run
it when the program ends, whatever way it ends.
Nothing is sent when there is nothing to send, or when the process never
began its Pigeon session: the flush sends only into a session the process
began at startup, and no recording covers an upload without one, so the
events stay unsent rather than going out unverified.
A delivery that fails at close is logged, never raised: the program's own
result (or its own failure) is what the caller gets, and the next process
cannot resend what this one lost.
What the app does with its telemetry when it closes: whatever the process accumulated and has not delivered is sent before the process is gone (owner decision, 2026-10-24: closing a simulated app is closing the app — pending telemetry goes out, then the connections close). The platform's entries run it when the program ends, whatever way it ends.
Nothing is sent when there is nothing to send, or when the process never began its Pigeon session: the flush sends only into a session the process began at startup, and no recording covers an upload without one, so the events stay unsent rather than going out unverified.
A delivery that fails at close is logged, never raised: the program's own result (or its own failure) is what the caller gets, and the next process cannot resend what this one lost.