Scheulded Jobs Hosted on IIS Not Always Firing

PowerShell Universal
1 
Product: PowerShell Universal
Version: 1.5.9

Hello,

First time poster here, I’ve searched around and found a few topics on this, but it seems I’ve tried most of the proposed solutions, so I’m a bit stuck.

I’m running PowerShell Universal on IIS and have two scripts that are scheduled to run, one at 6:00, and the other at 6:15am, and have noticed they don’t always run. It seems like all is well for a few days, but then they just don’t kick off and I have to manually run them. Below a screen shot of both my schedules.ps1:

image
image850×106 14.4 KB

I’ve also followed, https://docs.ironmansoftware.com/config/hosting/hosting-iis#idle-timeout, and made sure my “Idle Time-out” is set to zero.

I’m sure it’s just something simple I’m missing, but I just can’t seem to figure it out, any ideas?

Thanks!

2

I believe this is resolved in 1.5.12. I was having similar job/scheduler issues and they were resolved in this patch.
See the current changelog here: Changelog - PowerShell Universal

3 
Product: PowerShell Universal
Version: 1.5.16
Hosting: IIS

I’m having the same issue.

4

Can you make sure you’ve set the app pool settings to prevent it from stopping?

https://docs.powershelluniversal.com/config/hosting/hosting-iis#configuration-for-jobs

1 Like
5

All settings are confirmed.

6

Ok. You’ll also want to check for app pool recycles: iis - How to Find App Pool Recycles in Event Log - Stack Overflow

If the app pool is recycling, it can cause issues with scheduling.

1 Like