{"version":"2.1.299","anchor":"refused-internal-event-tracking-in-ccr-client","canonical_anchor":"refused-internal-event-tracking-in-ccr-client","heading":"Remote sessions stop sending follow-ups to events the server refused","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/refused-internal-event-tracking-in-ccr-client","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Remote sessions stop sending follow-ups to events the server refused\n\nIn remote sessions, Claude Code now remembers internal events the server refused and drops the entries that depended on them\n\n**What**\n\nIn a remote session, Claude Code sends a stream of internal events to a server. The server can refuse some of these. Claude Code now remembers which events were refused and drops any later entries that belong to a refused event instead of sending them.\n\nIt also changes when it skips repeated \"still alive\" signals (heartbeats) to the server: these are now skipped only for one kind of connection to the worker.\n\n**Why**\n\nEntries that depend on a refused event cannot be used by the server, so dropping them avoids sending data that would only be rejected or left without its parent.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}