Consider the following script.<BR><BR>&#060;%<BR>Option Explicit<BR>Server.ScriptTimeout = 30 &#039; seconds<BR>Response.Write "got here: " & Now & "&lt;br&gt;"<BR>Response.Flush<BR>Dim sleeper<BR>Set sleeper = Server.CreateObject("your_component_here")<BR>Dim i<BR>for i = 1 to 60<BR> Response.Write i & "&lt;br&gt;"<BR> Response.Flush<BR> sleeper.Sleep 1000 &#039; milliseconds<BR>next<BR>Response.Write "too far"<BR>Response.Flush<BR>%&#062;<BR><BR>The object I use results in a call to the Windows function Sleep. This should consistently timeout after about 30 iterations of the loop. But it seems to only timeout after 45 or so iterations. Lowering the timeout and raising the sleep amounts cause the page to rarely timeout at all. What gives? Also, if the Sleep amount is simply greater than the timeout, it does not get terminated at all. So I imagine that any COM call that takes a long time can sidestep the ScriptTimeout setting completely. Thoughts?