{"version":"2.1.292","anchor":"ccr-client-logs-undelivered-events-at-shutdown","canonical_anchor":"ccr-client-logs-undelivered-events-at-shutdown","heading":"Remote sessions log how many events were undelivered at shutdown","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/ccr-client-logs-undelivered-events-at-shutdown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Remote sessions log how many events were undelivered at shutdown\n\nAt shutdown, the remote-session client can log how many events went undelivered, as a warning if any did\n\n**What**\n\nWhen a remote session shuts down with the option to keep client events enabled, the client now writes a log line each time one of its event channels closes. The line gives the number of events that were not delivered:\n\n- a warning when one or more events were undelivered\n\n- an information message when none were\n\n**Why**\n\nWhen events go missing at the end of a remote session, the logs now show it, which makes the problem easier to track down.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}