Scheduled Jobs Fail to Execute After IIS AppPool Recycle

PowerShell Universal
1

I was having performance issues with PSU where it would eventually consume all RAM available on the system. As a workaround I would periodically recycle the IIS AppPool on my own during the day and things would keep on working. However, I tried to setup an automatic IIS AppPool recycle during a 2hr window where jobs are not scheduled to run. The issue is now some of the daily/weekly jobs are not running. There are no warnings/failures, literally the script execution doesn’t happen. Does recycling the AppPool cause Hangfire or other PSU components to not start clean again? Anecdotally if I open the admin console after restarting the AppPool jobs work without issue.

Examples:

Daily Job 01:

Snag_3b4c70b0
Snag_3b4c70b0777×184 12.6 KB

Daily Job 02:

Snag_3b4cb6b2
Snag_3b4cb6b2771×168 7.89 KB

Weekly Job (two missed executions):

Snag_3b4d6d30
Snag_3b4d6d301105×331 18.6 KB

Edit

Looks like the logs are showing the same behavior. AppPool recycle causes PSU to cease function until someone attempts to login to the web interface (or at least that’s what triggers it in my findings):

Snag_3b597f95
Snag_3b597f951053×1301 136 KB 

Product: PowerShell Universal
Version: 2.8.1
2

@OtherPeoplesCode

i have PSU hosted on IIS as well but i wont use AppPool recycle i recommend you create a script to stop AppPool wait like 30 sec and then start AppPool and create a scheduled task to run the script this is best practice based on research and experience.

3

I’ll give that a shot.