Email set to send-ignored because its size exceeds the value set in glide.email.outbound.max_body_bytesIssue Customers may encounter the following error even if the email body size does not exceed the value set in glide.email.outbound.max_body_bytes: "Email set to send-ignored because its size exceeds the value set in glide.email.outbound.max_body_bytes."FactsUnderstanding Email Body Size Limits: glide.email.outbound.max_body_bytes vs. glide.email.outbound.max_body_chars Overview When sending outbound emails in ServiceNow, the system may enforce limits on the size of the email body to ensure stability and performance. These limits are controlled by system properties such as: glide.email.outbound.max_body_bytes glide.email.outbound.max_body_chars However, their behavior differs in how the system applies these limits. This article clarifies the verification mechanism used for each and outlines how these properties interact. Key Behaviors 1. glide.email.outbound.max_body_bytes is Divided by 2 When this property is used to validate the size of the email body, its effective limit is half of its set value. The system applies a floor division by 2 during verification. Explanation: Even if the property is set to a high value, such as 100000, the verification will only allow a body size up to 50000 bytes due to the internal division. 2. glide.email.outbound.max_body_chars Uses the Full Value In contrast, this property uses the full set value for validation without any adjustment. Explanation: If this property is set to 100000, the system will validate against the entire 100000 character limit as expected. 3. Priority Between the Two Properties If glide.email.outbound.max_body_chars is defined, the system will ignore glide.email.outbound.max_body_bytes entirely. Implication: This means that the character-based limit will override any byte-based configuration. For environments with multi-byte characters (e.g., UTF-8 encoded content), this distinction is especially important.ReleaseAll ReleasesResolutionIncrease the value of the glide.email.outbound.max_body_bytes property to a higher value (e.g. double the current value) to avoid the error.Consider using the glide.email.outbound.max_body_chars property instead, as it does not have the same half-size limitation.Use glide.email.outbound.max_body_chars if you prefer precise control over text-based content length.Be aware that glide.email.outbound.max_body_bytes is halved internally, which may lead to unexpected truncation if not accounted for.Set only one of these properties to avoid ambiguity and ensure predictable behavior.