Lars Lervik

Thanks for the request! I added a ticket for us to look into this for a future release.

Thank you for all the information! The problem is that PowerShell 7's RecycleSchedule is set to "5". That setting is a Cron expression, and a single number isn't valid, so that's why the apps are failing.

While looking at this, I realize it isn't very clear in the UI; we'll change this soon to be more clear like it is with Cron Schedules.

For example, if you're trying to recycle every 5 minutes, you'd want to use "*/5 * * * *". Please try updating to a valid Cron expression and this should resolve the issue for you.

Thank you!

Hi @andreasmrvka, thank you for letting us know about this. I'm glad you were able to get this working in your environment. It appears that in some cases, old schedule values aren't cleared when editing which is causing the extra/invalid parameters in schedules.ps1. I've opened a ticket to fix this.

Hi @andreasweber, thanks for bringing this to our attention.

Could you send us (with any sensitive data redacted) the full log of one of the affected apps starting? Is there an inner exception in the log for the "CRON expression is invalid" error?

Are the failing apps on the same environment as the successful ones?

Could you please provide the Recycle Schedule from the relevant Environments' Advanced Properties? Do these settings differ between environments or between your prod and test setups?

You could use this script to retrieve all of the environments':

Get-PSUEnvironment |

Select-Object Name, RecycleSchedule |

ConvertTo-Json -Depth 2

I do notice a bug that if the RecycleSchedule is cleared out, it's not being interpreted as "off" and is instead submitting an invalid empty string. I've opened a ticket for this, but the above information should hopefully tell us if this the problem you're having or not. Thank you!

Thanks for letting us know how impactful this is. We've moved the fix for this into the next release (2026.3.2).

Thanks for bringing this to our attention! I've opened a ticket for it, and we'll have a fix in a release soon (sometime after 2026.3.2).

I've opened a ticket to investigate this. It seems fairly straightforward, but we will circle back if we need more information. Thank you!

Hello! Thank you for the request! Are there specific options/attributes that you're particularly interested in PSU supporting? I will add a ticket for us to look into this, and I want to make sure we have your use case covered.

Hi @michaelhanson1458, thanks for the request! This is coming in the UI refresh in our 2026.3 release.

Thanks for the request! These seem like really useful improvements to service resiliency. I've added a ticket to implement this in a future release.

Hi Jacob! Thanks for the feature request! I think we'll need to put some thought into this, as we don't currently sync configuration between PSU instances automatically. But it seems like a useful feature to add. I've added a ticket for us to look into this.

@Michael Taylor Thanks for the request! It will require some thought of how to integrate in PSU, but seems like a much nicer authentication experience. I've opened a ticket for this and we'll take a look soon.

This seems like it would be a good addition to the product. We'll look into the best approach to solve this.