Why would you get several hundred connections?
Maybe it was leftover from my earlier testing from before I included the .Dispose and .Disconnect at the end of the script. It seemed as though even when i ran the job the connnections would show up and not disappear for a little while. 100 jobs means 100 connections, but since they should each be disconnecting/disposing of the connection when done i'd assume they should drop off that list quickly.
Is there any known limit/threshold for the number of connections via clients/API/etc.. that the VisualCron Service can handle without causing issues? Thinking of organizations that might have jobs that run every minute or every 5 minutes and they have hundreds of jobs. Just thinking worst case scenario... you have 2500 jobs all running in a 5 minute period, all triggering this task as part of their notification/flow on complete.. Other than system resources getting angry at that many powershell instances in the background, what kinda limits would you say we're working within as far as VisualCron itself goes?
Brian