{"version":"2.1.247","anchor":"oversized-results-from-served-remote-requests-are-replaced-w","canonical_anchor":"oversized-results-from-served-remote-requests-are-replaced-w","heading":"Oversized results from served remote requests are replaced with an error","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/oversized-results-from-served-remote-requests-are-replaced-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Oversized results from served remote requests are replaced with an error\n\nOversized results returned to a cloud session are replaced with an error naming the size and limit.\n\n**What**\n\nWhen this machine answers work for a cloud session, results that exceed the size limit are swapped for a synthetic error result stating the result was too large to return, along with the actual byte count and the limit.\n\n**Details**\n\n- Served requests are tracked separately from other traffic, including which ones have already settled.\n- Results that were held for delivery can be given up when the connection is judged dead.\n\n**Evidence**\n\n`the result was too large to return`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}