30139: URL not valid for link shortening

This error occurs when ShortUrl is enabled and one or more URLs in the message are invalid.

URLs can be invalid for several reasons, the most common being improper encoding. Special characters must be correctly encoded, and every URL should include a valid scheme and host.

Make sure all special characters in URLs are properly encoded before use. Invalid URLs often result from unescaped characters that break parsers or violate RFC 3986

Examples:

Invalid: https://example.com/hola/mañana Valid: https://example.com/hola/ma%C3%B1ana (the character ñ must be percent-encoded)

Invalid: https://example.com/callback?token=abc123== Valid: https://example.com/callback?token=abc123%3D%3D (trailing = padding must be encoded)

Invalid: https://example.com/path%test Valid: https://example.com/path%25test (a raw % is illegal unless followed by two hex digits; %25 represents %)