Oversized results returned to a cloud session are replaced with an error naming the size and limit.
What's wrong with this entry?
When 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.
- Served requests are tracked separately from other traffic, including which ones have already settled.
- Results that were held for delivery can be given up when the connection is judged dead.
the result was too large to return
Strings lifted out of the shipped bundle, so the claim above can be checked against them.