sergioponstur
[2026.3.0] status filter in jobs does not filter
Same issue happening on my environment after upgrading to PSU 2026.3.1. When I select a job status filter, the job list is refreshed but the filter isn't applied. Is there any news regarding this bug?
Integrated mode intermittently fails with "You must be running this command in PowerShell Universal to use the integrated mode" after upgrading to 2026.3.0
Is there any update regarding this bug? I had to downgrade back to 2026.2.4 because my REST APIs weren't working. I have script calls that rely on the -Integrated parameter, even though the permissive mode is enabled in the appsettings.json, the script calls are running as unauthenticated and throwing an error message.
One Time schedules are not triggered on PSU 4
Hello everyone,
Since I upgraded from PowerShell Universal 3.8 to PowerShell Universal 4.0, I have been having an issue with one-time schedules.
Sometimes one-time schedules do not fire, they disappear from the schedule list after the time is reached, but they never fire. I have checked the system log under %PROGRAMDATA%\PowerShellUniversal, but I can’t find any logs of the job starting.
What I’ve noticed is that whenever I create a one-time schedule, it is not saved in the %PROGRAMDATA%\UniversalAutomation\Repository.universal\schedules.ps1 file, while other schedules, e.g. cron schedules, are always saved in this file.
I added a one-time schedule to the file and it was triggered, while schedules created via the REST API or manually on the web interface aren’t always triggered.
Also, after restarting the PSU service, all one-time schedules disappear completely from the web interface.
Product: PowerShell Universal
Version: 4.1.8
Running on IIS and LiteDB.