If the user is an IE user, that may be the problem. There is a timing issue on some pages where IE tells MathJax that the page is ready before it actually is, and so MathJax runs before the math is actually loaded into the page. One solution is to add
if (MathJax.Hub.Browser.isMSIE) {
window.onload = function () {MathJax.Hub.Queue(["Typeset",MathJax.Hub])}
}
to your x-mathjax-config script and this should take care of the problem for IE users.
If it's not an IE user, then can you give more details about the situation?
Davide