I can't display my strategy page. Browsers Chrome and IE 10 indicate a script is running. This was Sunday 12/1 between 7:30 and 8:20 p.m. (in case there was maintenance). The S&P 500 strategy displayed successfully on Friday 11/29, the last time I posted signals.

More Info: The top of the page displays, but if I try to scroll down the page (in IE 10), a pop-up banner says, "Wealth-Lab.com is not responding due to a long-running script"

Interesting - it only happens on my S&P 500 strategy (where it happens every time). My Small Tech strategy loads fine.

Both strategies are loading just fine now. Could be a temporary glitch (a browser's or website's).

P.S. Please use the WealthSignals forum in the future for WS specific questions:

Trading System Author's Support

The strategy does not load for me. It hangs running a script. If I click on "Stop the script", the page reloads and eventually hangs again, an infinite loop. The only way out is to kill the browser. Windows 7, IE 10 (though Chrome has the same problem) Low CPU utilization, but IE has 5000 byte/second traffic. What does the script do? Was it changed recently?

Chrome gives another clue, a popup having the text: "The page at www.wealth-lab.com states AjaxExceptionResults"

I thought about the category to post this. It seems to be a web, not a strategy, issue and Wealth Signals does not have a web issue category.

We'll double check, please stay tuned.

Please try in Firefox.

P.S. Have you recently upgraded Adobe Flash plugin?

Firefox - I don't have installed. Before I install Firefox, can you give me a probability that it will fix this? How many browsers do I need (grumble, grumble)?

Yes to Adobe Flash upgrade, why? Actually, the problem occurred first. I only re-installed Flash as my attempt at fixing this.

I thought you might have FF installed, but since you don't, let's leave it out for now.

Re: Flash. We're looking into the issue, collecting bits of information here and there. Flash might have (or have not) to deal with it.

This issue has been fixed. Apologies for the inconvenience!