I've had a vaguely similar occurance once that took forever to track down. When I would persist a particular model back to mysql, I would fire off a job in Gea

I've had a vaguely similar occurance once that took forever to track down. When I would persist a particular model back to mysql, I would fire off a job in Gearman, that would then grab the saved object and asyncronously send it off to lots of other sources. After moving servers it would always send the previous state of the object. Having previously worked flawlessly. Eventually I trackked it down to the fact that my Gearman job was being kicked off before the actual write to MySQL, so then when I did the select in my job process, it would grab the previous snapshot. Pretty easy fix once I figured that out.