Configurable Delay Between Schedule Tasks

[ryanamiller]

Right now when attempting to schedule a Process on a Resource Machine using the Login Agent, 2 schedules are needed: Login Schedule Runs login agent Process Schedule Runs 5 minutes after Login Schedule to enable runtime resource startup script to complete Has tasks for any Processes that need to run followed by a Logout task This causes duplication of schedules and inflates the number of schedules needed in the Control tab, which is already not easy to navigate if you have many schedules. Suggestion would be to have an option to add a Task that within a Schedule that doesn't assign a Process to a Resource Machine, but simply waits for a configurable amount of time (seconds). This would allow for 1 Schedule to be created with the following tasks: Process Schedule Login Agent Task New configurable wait Task Process Task Logout Task This would remove the need to create double the amount of Schedules, simplify configuration when using the Login agent, and allow for more flexibility within a Schedule.  

[Denis__Dennehy]

I totally agree.  Or even better, have a wait option that waits for a 'real' resourcepc to exist on the resource (rather than the login agent resource)

[MarcinSzaroszyk]

I have the same problem with schedules. Great idea.

[jasperverhaart]

We are exploring the use of resource pools and encounter the same issue here. 1 schedule seems required in order to have the scheduler assign both the login and process steps to the same resource within the resource pool. Especially because we use different windows user for different processes. Is there a solution available for this? Or a workaround for the time being?      

[ryanamiller]

This proposed solution would also allow configurations that utilize the Login Agent to use Resource Pools as well.  They could have one Schedule configured which logs in using the Login Agent, has the configured wait task, and then subsequent tasks which run on the automate.exe process.

[Wendy__Braem]

We also have duplication in our scheduer. First login and 2 minutes later the process. We would like to see they are related. If 1 is ready, the other will run.