{"version":"2.1.275","anchor":"poll-event-kind-now-format-validated-and-per-kind-size-cap","canonical_anchor":"poll-event-kind-now-format-validated-and-per-kind-size-cap","heading":"Poll event 'kind' now format-validated and per-kind size-capped, wording of reserved-kind error changed","tier":"internal","area":"Poll Events","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/poll-event-kind-now-format-validated-and-per-kind-size-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Poll event 'kind' now format-validated and per-kind size-capped, wording of reserved-kind error changed\n\nPoll events now validate their 'kind' field format, cap size per kind, and can carry media\n\n**What**\n\nInternal poll events (used for delivering updates) now have stricter validation on their `kind` field:\n\n- `kind` must match a pattern of a lowercase letter followed by lowercase letters, digits, or hyphens, up to 64 characters, and events that don't match are rejected with a new error message\n\n- the maximum envelope size is now looked up per `kind` instead of using one fixed limit for all events\n\n- the error message shown when a reserved kind is used has changed wording, now referring to a \"trusted in-process producer\" instead of a \"server-authored producer\"\n\n- poll events can now optionally carry a `media` field\n\n**Why**\n\nThe stricter format check and per-kind size limits make poll event handling more precise and harder to misuse, and the new `media` field lays groundwork for events to carry attachments.\n\n- Area: Poll Events\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}