UnionSystems wrote
The issue you need to be “aware” of is that the scheduler only ever has one instance of it running. If the scheduler initiates a process that takes more than 1 minute to complete then it will skip starting (the scheduler) in the next minute.
This is incorrect. The scheduler runs about every 60 seconds no matter what.
I have about 20 processes under the scheduler control. I want these processes to run as often as possible, so I do not have any conditions based on time when they can run. On a busy day, it can take several minutes for all 20 processes run. I have the system set up so that I can monitor these processes and I can see several processes running at the same time.
About the only condition I have on these processes is that the same process can not have more than 1 instance running concurrently. To prevent this, I keep track of when each process starts and stops and the scheduler checks if a particular process is stopped before starting it again.
