Workflow - cannot schedule or invoke 2026.2.0
Just upgraded to 2026.2.0, playing about with Workflows and when I schedule a workflow it doesn't fire.
Log gives this error:
Scheduling job 'test' with schedule sdfsdfsdf on time zone (UTC+00:00) Dublin, Edinburgh, Lisbon, London
2026-06-05 09:46:37.774 +01:00 [WRN][Hangfire.AutomaticRetryAttribute] Failed to process the job '25': an exception occured. Job was automatically deleted because the retry attempt count exceeded 0.
System.NullReferenceException: Object reference not set to an instance of an object.
at PowerShellUniversal.Automation.ExecutionService.Execute(ExecutionOptions executionOptions) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal.Automation\ExecutionService.cs:line 145
at InvokeStub_TaskAwaiter.GetResult(Object, Object, IntPtr*)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Also, attempted to work around it by creating a script with Invoke-PSUWorkflow as per PSU documentation and schedule that up, but I get "The term 'Invoke-PSUWorkflow' is not recognized as a name of a cmdlet, function, script file, or executable program."
Seems as though that cmdlet is not included despite the documentation thinking otherwise..?
Get-Command -Module Universal | Where-Object Name -like '*Workflow*'
CommandType Name Version Source
----------- ---- ------- ------
Cmdlet Get-PSUWorkflow 2026.2.0 Universal
Cmdlet New-PSUWorkflow 2026.2.0 Universal
Cmdlet New-PSUWorkflowActivity 2026.2.0 Universal
Cmdlet New-PSUWorkflowParameter 2026.2.0 Universal
Cmdlet Remove-PSUWorkflow 2026.2.0 Universal
Cmdlet Set-PSUWorkflow 2026.2.0 Universal
All Comments (5)
@timgo I opened a couple issues for this. It looks like Invoke-PSUWorkflow isn't exported from the module manifest. As for the object reference exception, I'm not sure why this would be happen but I'll circle back once we start looking into it to see if we need more information.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
Thanks @Adam Driscoll much appreciated!
Just to say script scheduling is working fine, and I can invoke the workflow manually in the gui, it is specifically when using a schedule (or even triggering the schedule itself manually)
@timgo Sounds good! I'll make sure we take that into account when tracking this down.
What are you trying to do with workflows? I'm just curious. This is certainly just a foundational release for them so if you have any feedback, let me know. We have some ideas but the best ideas come from users.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@Adam Driscoll can't tell you how much I've been looking forward to workflows! And scheduler issue aside they work really well.
Initially I have just done a certificate renewal workflow using poshACME (step 1 renew, 2 copy to central cert store, 3 copy to Azure key vault, 4 copy to Azure storage blob, 4 reload nginx containers).
We also have a routine to extract info from our CRM system SQL DB and sync it to a CosmosDB. I was just about to move that to workflow when I found the scheduler bug
But I plan to do so much more, its actually good timing as we are going to begin migrating customers from our antiquated SaaS platform to a nice shiny new one in a couple of months, I have done a set of migration scripts and had been writing a complex conditional execution script for them all which would be fronted by an app asking which migration steps to perform..with workflows that's not required I can just populate the individual scripts on the workflow, add some conditional ps expressions to each step to determine if its executed, and have the app invoke the workflow.
And from there the world is my lobster, from simple things such as user credentials management for our HD team, to things like deploying new customers and upgrading existing ones which would be 20 or more step processes (which would just be incredibly hard without workflow!)
If there is one feature I could point to for the future, it would be conditional branches when building the workflow in the gui..on success invoke script x, on fail script y, on complete script z - azure data factory is a perfect example of this.
But even now it's fantastic and thank you for introducing it!
@timgo Cool! I love hearing a use case like that. Glad you like the ability to do PS Expressions for parameters. We thought branching might be up there so we pulled it into the next milestone. We haven't started work on it yet but hope to get it in there. I'll make sure to share this with the team so they can see the vision.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
