In some situations, a synch update made previously is reverted by ConnectALL without any user action being performed.
This can be caused by a situation referred to as stale cache. This can happen when there is a partial failure that happened due to issue linking with successor / predecessor mapped to invalid type. Then the transaction processed will not be there in cache and the cache will become stale. In such case if the record is processed again, it will roll back the data.
For example, if a status transition happens from Jira to Rally along with the invalid issue link type with predecessor then the status value become stale in cache.
This issue is resolved in 4.1.1