{"version":"2.1.242","anchor":"cloud-session-event-posting-returns-structured-outcomes","canonical_anchor":"cloud-session-event-posting-returns-structured-outcomes","heading":"Cloud session event posting returns structured outcomes","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/cloud-session-event-posting-returns-structured-outcomes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Cloud session event posting returns structured outcomes\n\nCloud event posting now distinguishes a dead session from a network failure.\n\n**What**\n\nPosting an event to a cloud session now returns a named outcome instead of a value or null, so an event sent to a session that is no longer running is distinguished from a network failure.\n\n**Details**\n\n- Outcomes: accepted (with a sequence number), session inactive, or failed with a cause separating HTTP, timeout and network errors.\n- An inactive session logs \"(session not active)\" and increments a `remote_send_event_session_inactive` counter.\n- Control responses can now supply their own message identifier and are counted as sends.\n\n**Evidence**\n\n`remote_send_event_session_inactive`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}