Null Wait Job
Instead of using Windows job type and run line of TIMEOUT or genericp to create a pause - Could this be a Null type feature instead? Instead of running pauses on my IBM or Windows agents - I just need pauses or waits in the overall processes.
Collecting community feedback Automation Brick Suggested by: Nick Wilcox • Upvoted: 06 Oct, '22 • Comments: 4
Francois EYL Admin
Thanks Nick for submitting this idea. I can see where and why this would be useful. It does not match our current short term priorities, but I leave it here to collect more feedback/votes from the community - we'll reevaluate when priorities change.
Out of curiosity, how many of these jobs would you estimate you currently run in production (a number per day)?
We would also find this useful. We use a ton of delay jobs to ensure an event is processed by SAM before we continue on with our workflow.
Yesterday, we had 174 of these jobs run in our production environment.... Given the purpose of our delays and the switch to task based licensing, it seems odd to pay for a job whose purpose is simply to give OpCon enough time to do its job.
On Friday we had 276 of these jobs run. That's only counting Container Job / Sub schedules uses as once too. We use these for two purposes, one where we drop files or wait for processes to complete, before running a File Arrive or SMArt Email to check for confirmation. It's making me rethink if I should get rid of the waits, as those are usually the minimum wait time, but I'd have to run the File Arrive or SMArt Email with a TON of restart logic, to keep checking.
The other use for them, to Brady's point - I can't parse a file, that applies properties to the schedule and immediately use them. There's a small bit of processing time before they add / apply before they can be used. Otherwise I kept running into the issue where the job would go into the hold status. I couldn't risk that occurring overnight for ACH processing. I also use waits, with events to just flip Self Service Button statuses. I don't like to run 20 Events at once time and risk a critical button not showing.
I used to do pauses with a NULL job as an admin back in the day but there are some limitations. Make a NULL job with an auto-restart X minutes after the completion. The downside here is that the minimum amount of time to wait is 1 minute (and sometimes you may only need it to be 10 seconds etc).
You could also create a NULL job with an expression dependency based on another jobs completion time + X seconds (you could also not use a NULL job and just do it on the next job but sometimes its nice to have the visual for where the pauses are located).