Hi Ahmed,
Sorry it's giving you trouble. I've never had it abort for me, except on WolframCloud. My laptop is a Mac. Since you're at Wolfram, I assume you know about the dynamic timeout limit. But for me, the dynamic content takes about a second, certainly less than two seconds, to update (counting Mississippis to myself). Anyway that's less than the timeout (which I believe is 5-6 sec.). But I believe the result of the timeout is usually$Aborted
, which is why I thought of it.
I don't really know how to time it on wolframcloud.com. The initial evaluation takes 17-18 sec.; updates take 5-6 sec. (measured between click on the webpage and rendering). It usually does not abort, although it has aborted on the web.
Thanks for your interest. If you happen to discover something funny I did in my code, please let me know. I thought I doing fairly normal operations.
Michael