Job with DirWaitForUpdate Aborts if Started via RunNow

I have a job that contains the DirWaitForUpdate command. If it is started by 24x7 at startup time (it is designed to run continually), it works fine. But if I start it from the Scheduler with Run Now, it aborts after a short while on the DirWaitForUpdate command:

5/11/2007 14:06:52 2 283 0 DatRP An error occurred while executing automation script: Line 204: The handle is invalid.

Is there a known cause for this? Or is there a workaround?

The job loops looking for files in a directory and waits at the DirWaitForUpdate for more files. I put some diagnostics in the job and found that it would only loop once or twice before aborting if started via Run Now.

I am not sure if I can help you with this right away. Please email your script to support@softtreetech.com for further review.