This article was updated 31st October 2009 to correct hyperlinks.
 
Detached TableLevel Scripts are created in the same way as TableLevel scripts, except you select Detached Table Level from the Script Type list when completing the Table Script details.

Unlike TableLevel scripts, Detached Table Level scripts are not run immediately but within a predefined amount of time. This enables the system to store a queue of scripts that need to run, and it means that a user does not need to wait for a script to complete.

I have discussed Detached TableLevel scripts previously in the article "TableLevel Scripts and SQL TimeOuts".

This type of script is useful when the execution of the script is likely to be time consuming and you don’t want the user to have to wait. The users do not see errors as they happen. The Log file must be viewed for any diagnostic errors.

Detached Tablescripts are checked every 300 seconds by default. The firing of the scripts will show in the logs. The check happens at a different time to the Escalation rules.

This can be controlled by adding a new Registry Sting Value called DelayedTLSInterval
to the values of the key HKEY_LOCAL_MACHINE\SOFTWARE\eWare\Config\/CRM

You can therefore override the 300 second default with another value e.g. 400 or 500.

If you want to turn off the checking of the delayed scripts, then you can just set the key value to some a non-number value, like X or Stop, that should crash DTLS out without any other side effects.

Once the key has been added you must then reset IIS and the effect will kick in.