Product: PowerShell Universal
Version: 5.5.5
Hey PSU folks,
I have an environment where Okta workflows will call PSU APIs, which will create a JSON “staging” file in a folder relevant to the API/script. From there I have job scripts on schedules that run so often, check for staging files, and when found the scripts import them and take actions.
Grand total I have 14 scheduled jobs running per hour. When there’s no staging files, the scripts simply exit and there’s very little written to the PSU Jobs. When there are staging files, they import them, take actions, and most things are written to the PSU Jobs stream and logged in the PSU Jobs.
At first, I had no issue with the Automation / Jobs page loading all the jobs. Here lately the Jobs page will not load and just sits there spinning like it’s trying to load the jobs data, but it won’t. Usually on a reboot the jobs will load for a day or two, but after that they will not.
When I click on Automation / Jobs and it’s trying to load the Jobs, I notice the resource usage on the server starts climbing until there are no more resources. I doubled the resources on the server, but that didn’t help.
Also, when I click on Automation / Jobs and it’s stuck spinning I can’t click out of it. I’ll click something else and the URL in the browser will update, but it will not browse to the newly clicked location. I then have to click refresh on the browser for it to leave the Jobs page and go to the newly clicked page.
Note that in my Sandbox environment we have an exact copy of this setup, except the schedules are disabled and we manually trigger the job scripts there. That environment loads the Jobs page every time without issue, but there are far fewer jobs in that environment.
Any ideas? At 14 scheduled jobs per hour, am I simply writing too many jobs for it to load them? Is there some sort of limit, roll over, or other settings I can configure to keep only 14 days’ worth of jobs, so they load?
Thanks,
Rob