The drawbacks of running 200 jobs through a single JOBS object include;
It will be harder to isolate the run history for any particular application.All 200 jobs will share the same documentation tab.You might find there are other AE features that you would like to use on some but not all of your jobs.
For these reasons I would consider cloning your JOBS 200 times. We typically clone, except for common utilities like FILE.COPY, FILE.DELETE, etc.Regarding how to bulk resubmit/unblock, I think the user interface already supports some multi-select operations in the ProcessMonitoring view? And it also might be possible to write a script to automatically perform these operations in bulk? I would also be thinking about ways to stop Automic from initiating more tasks when one of these serious faults occur, for instance when a serious fault is detected close the queues for example.
I like Joel's idea of ditching promptsets, and using the variables area instead. This avoids the prompting behavior upon restart.
Hi AmeyYou do not have set the "Generate at runtime" option for these jobs (see object attributes).If you use AE script (:WAIT) the script is evaluated during the generation phase. If you start a workflow, all jobs within that do NOT have set "Generate at runtime" are being generated. This causes the :WAIT instruction to be executed before the first job even starts :-).If you must have this setting enabled for whatever reason, replace the :WAIT logic with an OS-Job alternative like "sleep &NUM_SEC#" on Unix. These instructions are always executed during runtime.Regards