<?xml-stylesheet type="text/xsl" href="https://uat.community.rws.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SDL TMS 11.0  |  Incorrect handling of timeouts on SDL TMS multi-server environments</title><link>/product-groups/translation_management/tms/b/sdl-tms-11-product-updates/posts/sdl-tms-11-0-incorrect-handling-of-timeouts-on-sdl-tms-multi-server-environments</link><description>Symptoms: In a multi-server environment, sometimes when a timeout occurred on server A and server B picked up the tasks, the sequence of actions happening at database level were managed badly, generating an overlap. This overlap led to the creat...</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator></channel></rss>