Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


kdcarlisle
2010-01-13T23:40:10Z
Currently a job can run either asynchronous or synchronous. It would be nice to be able to limit the asynchronous jobs.

I have a job that uses a file trigger. When the job runs a powershell script is used to process the file. A file is uploaded and the job runs (everything works). We upload a few files and everything still works fine. However, when I upload a lot of files (more than 200), the machine runs low on memory and VisualCron starts throwing errors.

I understand that I can run the job in synchronous mode to get around the problem, but it would be nice to allow it to run asynchronous up to a limit of x jobs (and queue additional jobs and process as other jobs complete).
Sponsor
Forum information
Scroll to Top