{"version":"2.1.234","anchor":"overlong-message-recipients-are-rejected-by-the-schema","canonical_anchor":"overlong-message-recipients-are-rejected-by-the-schema","heading":"Overlong message recipients are rejected by the schema","tier":"internal","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/overlong-message-recipients-are-rejected-by-the-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Overlong message recipients are rejected by the schema\n\nAn overlong recipient name in the messaging tool now fails validation right away.\n\n**What**\n\nThe messaging tool's recipient field gained a length bound alongside the existing single-line check, so an overlong recipient fails validation immediately rather than later during resolution.\n\n**Details**\n\n- The rejection message says the value \"must be a single-line recipient name or address\".\n\n**Evidence**\n\n`must be a single-line recipient name or address`\n\n- Area: Session Messaging\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}