The ingest verb's refusal list is unbounded in count. renderRefusals joins one entry per refused item into the durable refusal reason, and RunRecord.RefusedItems keeps one entry per refused item, with the item count payload-chosen — so a payload of many illegal items produces a refusal record and a terminal message hundreds of kilobytes long. The per-name cap on quoted field names states the principle exactly and does not apply to the refusals themselves.

The ingest verb's refusal list is unbounded in count. renderRefusals joins one entry per refused item into the durable refusal reason, and RunRecord.RefusedItems keeps one entry per refused item, with the item count payload-chosen — so a payload of many illegal items produces a refusal record and a terminal message hundreds of kilobytes long. The per-name cap on quoted field names states the principle exactly and does not apply to the refusals themselves.

Grounds

• pursued: a per-value cap bounds nothing when the payload chooses how many values there are, and a record whose purpose is to be read has to stay readable; a refusal record of hundreds of kilobytes appearing again would show this wrong