{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-resumes-a-streamable-mcp-http-session-after-a-backpressure-induced-drop",
  "title": "What happens when an instance resumes a streamable MCP HTTP session after a backpressure-induced drop",
  "date_of_record": "2026 November 18",
  "scope": "Applies to MCP servers using the HTTP-native streamable transport with `Last-Event-ID` resumption and per-session event buffers. Does not apply to stdio transports, nor to servers that advertise resumability but discard events on disconnect.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-resumes-a-streamable-mcp-http-session-after-a-backpressure-induced-drop.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-resumes-a-streamable-mcp-http-session-after-a-backpressure-induced-drop.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-resumes-a-streamable-mcp-http-session-after-a-backpressure-induced-drop.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1086,
    "python_slice_tokens": 256,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The MCP streamable HTTP transport conflates two distinct guarantees under a single \"resumption\" label: *event replay* (the server can re-emit events after a given `Last-Event-ID`) and *session continuity* (the server retains session state, including in-flight request IDs and backpressure accounting). A client that reconnects with a valid `Last-Event-ID` may ...",
    "what_was_observed": "A client streaming a long-running tool invocation via SSE encountered TCP-level backpressure (the server's write buffer filled because the client's read loop stalled during a local GC pause). The server, applying a bounded per-session event buffer, began dropping events and eventually closed the stream with the session marked as *resumable*. The client reconnected with `Last-Event-ID` pointing at the last event it ha...",
    "condition_of_validity": "Resumption is only semantically valid when all three hold: (1) the server retains the session object for at least as long as the event buffer, (2) the `Last-Event-ID` the client sends reflects the last event *processed*, not merely *received*, and (3) backpressure-induced drops are recorded as gaps rather than silently skipped. If any condition is violated, ...",
    "decision_boundary": "On reconnect, the client must not trust stream re-establishment as proof of session liveness. It must issue a liveness probe (a cheap request with a known correlation path) and verify a response before resuming normal traffic. If the probe is rejected or times out, the client must treat the session as dead and re-initialize rather than replay. The server, sy...",
    "operational_effect": "Teams that adopt streamable HTTP resumption without a liveness probe observe a characteristic failure signature: sessions that appear connected, emit events, and never complete. The correlation maps grow unbounded because the client keeps generating responses to dead request IDs. The fix is not in the transport but in the client's resumption protocol: probe-..."
  },
  "matched_failure_symptoms": [
    "HTTP_429_BURST_STARVATION"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "a2a69628025f3e8ed2f6e3aa56e824196a543b3a72550e1e32a7fd51866cd6cd",
    "verified_classes": [
      "ResumptionSemanticError",
      "ResumableSession"
    ],
    "verified_functions": [
      "__init__",
      "resume",
      "probe",
      "require_live"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ResumptionSemanticError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
