Schedules do not work in 5.4.0

PowerShell Universal
1 
Product: PowerShell Universal
Version: 5.4.0

We are experiencing odd behavior in this version. I’ve had schedules start twice in a row and then never again, and it seems like I can’t get any to start now, even if I make new ones. I’ve checked all of our configured environments, tried new ones… nothing seems to work.

I do see errors in the systemlog:

2025-03-12 18:55:04.663 -04:00 [WRN][Hangfire.AutomaticRetryAttribute] Failed to process the job '70': an exception occured. Job was automatically deleted because the retry attempt count exceeded 0.
System.Exception: Invalid queue name.
   at PowerShellUniversal.Automation.JobDispatcher.Execute(ExecutionOptions executionOptions) in D:\a\universal\universal\src\PowerShellUniversal.Automation\JobDispatcher.cs:line 105
   at InvokeStub_TaskAwaiter.GetResult(Object, Object, IntPtr*)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

The “Next Execution Time” for the CRON job was working, until the trigger fired I guess, now it says “Never”.

Also, at the top, the version icon that says “5.4.0” is yellow. I believe it used to be green in 5.3.3 - but when I click it there is no indication that anything is wrong/warning. All the healthchecks are green. I’ve restarted the service and the service, no change.

2

I’ve not tested schedules on my dev installation of 5.4.0 yet, so can’t confirm if it’s a local issue for you or a more widespread problem.

As for the version indicator, green means there’s an upgrade available and yellow means you’re up to date.

It would probably be clearer if another element was displayed alongside the current version that displayed something like ‘v5.4.1 update available’ that linked to the downloads page or the change log.

3

I can reproduce this problem with schedules when I set the schedule to a specific computer. We’ll have a fix for this coming in v5.4.1. It’s a small change. That should be out tomorrow AM. There was also a .NET SDK CVE we are patching for.

1 Like
4

Looks like schedules are working now, thank you! I’ve tried with both CRON and simple schedules.

The only difference I notice is that simple schedules appeared to be delayed based on the start time previously, but now it appears to be based on the end time. Simple schedules that used to run every 5 minutes (with 4 minute runtimes) now actually run every 9 minutes. CRON work as expected, so we will likely swap a few schedules over to that instead.