The material provided is for informational purposes only, and should not be relied on in making any purchasing or investment decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. © 2026 Cloud Software Group, Inc. All rights reserved
Hi Jason,
Could you provide more info?
Which client? which operation? In which context?
Which one is the reason the ticket is malformed?
Thanks
Ideally, this should not be needed but we've encountered issues where network components have interfered with TLS session resumption handshakes, resulting in failed connections. Therefore improved error trapping and recovery (e.g. by initiating a full handshake on any TLS error) would be beneficial under these circumstances.