Job timout issue

Also the two jobs that failed due to a handshake issue spawned at the same time? Could be this be a collision error? @Patrick Ouimet
We reviewed our EDR logs and nothing was interfering or blocking these processes from running.
PSU 2026.3.4 – PowerShell 7 handshake failures and internal gRPC connection errors
Not sure if this is related to our issues as well. We are on a different version though. https://forum.devolutions.net/topics/57219/job-timout-issue#247681
Job timout issue
Do you have an email i send you those logs? I got your email for the file upload but its making me create an account and MFA and all that jaz
The system log that covers one failed job, from %ProgramData%\PowerShellUniversal\Logs\System, with the time of the failure.
I have attached the logs. The job that failed was "Boarding\Get-TerminatedEmployees.ps1"
```
[00:03:23 VRB][Automation][190443] [INF] [32;1mTeamsAPICall : [0mSuccessfully Invoke-RestMethod
[00:03:23 VRB][Automation][190443] [INF] [32;1mId : [0m190440
[00:03:23 VRB][Automation][190443] [INF] [32;1mComputerName : [0mESPR10617
[00:03:23 VRB][Automation][190443] [INF] [32;1mReason : [0mError executing job: PowerShell did not respond in a timely fashion. PowerShell Universal is currently waiting 120 seconds for PowerShell to start running the script.
[00:03:23 VRB][Automation][190443] [INF] You can increase the timeout by setting the 'Job Handshake Timeout' setting in the Settings \ General \ Automation page.
[00:03:23 VRB][Automation][190443] [INF] If you are still experiencing issues, you may need to consider increasing the resources available on your system or take advantage of the Random Delay parameter for schedules to stagger jobs.
[00:03:23 VRB][Automation][190443] [INF]
[00:03:23 VRB][Automation][190443] [INF] [32;1mScript : [0mBoarding\Get-TerminatedEmployees.ps1
[00:03:23 VRB][Automation][190443] [INF] [32;1mStartTime : [0m11/1/2026 5:00:36 AM
[00:03:23 VRB][Automation][190443] [INF] [32;1mTeamsChannel : [0mBoarding
[00:03:23 VRB][Automation][190443] [INF] [32;1mEndTime : [0m11/1/2026 5:03:19 AM
[00:03:23 VRB][Automation][190443] [INF] [32;1mIdentity : [0m
[00:03:23 VRB][Automation][190443] [INF] [32;1mParameters : [0m{[All, <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04">
[00:03:23 VRB][Automation][190443] [INF] <B>true</B>
[00:03:23 VRB][Automation][190443] [INF] </Objs>]}
[00:03:23 VRB][Automation][190443] [INF]
```
Whether the failing jobs use a Run As credential, and which environment they run in, for example PowerShell 7 or Windows PowerShell 5.1.
This is running from powershell 7 and not using a run as
Whether PowerShell Universal runs as a Windows service or under IIS, and how many nodes share the SQL database.
Psu runs as service. 1 node
Roughly how many jobs start at the same time when the failures happen, and whether the failures cluster at certain times or on one node.
This is a child job that is called by "Boarding\Process-BHRTermsList.ps1" which is a scheduled job that runs at midnight on the 1st and the 15th of each month
I asked copilot to summarize my schedules.ps1...
Yep — in .universal\schedules.ps1 I counted:
• Total scheduled jobs: 42
• Scheduled at midnight (00:00): 15
• Scheduled at the same time as at least one other job: 29 jobs across 5 shared time slots
Shared slots I found:
• 0 0 ... → 15 jobs
• 0 8 ... → 7 jobs
• 0 6 ... → 3 jobs
• 0 */2 ... → 2 jobs
• 0 7 ... → 2 jobs
When this started, and whether anything changed around that time, such as an upgrade, an antivirus update, new schedules or server changes..
Nothing changed.
Job timout issue
I sent the email yesterday afternoon
Job timout issue
Currently running 2026.2.5 in prod with sql as the backend and we started randomly getting the following.
Error executing job: PowerShell did not respond in a timely fashion. PowerShell Universal is currently waiting 120 seconds for PowerShell to start running the script. You can increase the timeout by setting the 'Job Handshake Timeout' setting in the Settings \ General \ Automation page. If you are still experiencing issues, you may need to consider increasing the resources available on your system or take advantage of the Random Delay parameter for schedules to stagger jobs.
We can usually just re-run these jobs but this is a workaround at best.
PowerShell Universal Community Call - October 2026

I think you guys are following the same dark mode as the other devolutions products, but I do prefer how vscode and other apps use a darker tone. Devolutions is bluer. Maybe we could have a theme picker?
PowerShell Universal Community Call - October 2026
@michaelhanson1458 As in the syntax highlighting or the UI in general?
@Adam Driscoll
I think its the blue shade mainly.
PowerShell Universal Community Call - October 2026

This could use some work
PowerShell Universal Community Call - October 2026
Better dark theme support for admin console
Dashboard - invoke-psuscript error
Thank you for the update
Dashboard - invoke-psuscript error
I have been using pages within psu apps and when using cmdlets like the following
$job = get-psujob -id 1234123 -Integrated
$Job = Invoke-PSUScript -Name "test"
in the page i get the following

This works fine on 2026.2.5 but does not work on 2026.3.0
Clicking on discover environments
yes sir
Pester test still are not working in 2026.3
Done
Pester test still are not working in 2026.3

Clicking on discover environments
Object reference not set to an instance of an object.
at PowerShellUniversal.Automation.PowerShellResolver.GetInstalledVersions() in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal.Automation\PowerShellResolver.cs:line 114
at PowerShellUniversal.DiscoverEnvironmentsButton.Discover() in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Shared\Settings\DiscoverEnvironmentsButton.razor:line 38
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at AntDesign.Button.HandleOnClick(MouseEventArgs args)
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
Workflow UI bug with clicking form activity palette
See attached video
Sessions: add which node/computer the user is connected through.
Sweet thanks
Cache size
Sweet. Thanks
Clicking on the column picker under jobs throws the following error.
No this was found in my dev instance of PSU. However, its running the same version of psu and the only difference is one is prod is using sql and dev is sqlite
Sessions: add which node/computer the user is connected through.

Clicking Child Jobs shows blank page
Sent you the email.
Clicking on the column picker under jobs throws the following error.

No column selector for the scripts view?
Thanks dude
Clicking Child Jobs shows blank page
Thanks
Cache size

I think it would be nice to see how large a specific cache item is in the DB. for example how large is your dataset for something like caching all ad user objects