Ok this is very embarrassing… The original solution with the timezone did fix this issue. The continued issues we were seeing were due to a recent change in our deployments, we were just deploying an old release 
. We only deploy once a week or so otherwise I think we would have caught that sooner.
