Just to follow up, we migrated from 3.8.7 to 3.8.10 and that fixed our issue. The Encode library stayed at the same version number (2.43). I am guessing that the problem was in some RT code. Anyway, we are not seeing the error anymore. Cheers, Thierry