We fixed the issue with the Get-PSUJob cmdlet in the main branch (will be in 1.5.1) but still investigating the never end date. Looks like if you actually set the app token too far in the future ASP.NET core gets mad and doesn’t validate the token. Looking into that one still.
btw I’m facing another issue with Invoke-UAScript / Invoke-PSUScript even tho the call is correct, was working flawlessly on 1.4.9 those call ain’t working anymore.
We are running into this same issue and error message when trying to run Invoke-UAScript. I tested with both scripts that have parameters and those that don’t, but neither works. All of our API’s that call UA scripts are broken since the upgrade to 1.5.1.
if you do Invoke-PSUScript -Script (Get-PSUScript “test.ps1”) / Invoke-PSUScript -Name (Get-PSUScript “test.ps1”) or / Invoke-PSUScript -Name “test.ps1” it works
if you do Invoke-PSUScript -Script “test.ps1” as per the examples it doesn’t … weird !
This will be fixed in tonight’s nightly. We will likely be releasing 1.5.2 after some additional validation. We’re working on a large set of integration tests so that something like this doesn’t happen again.
Thx a lot for your reactivity, much appreciated, I’ll be able to present the dashboard on monday.
I have another question for you, I noticed that everytime I create a new script or edit / save a script the dashboard are restarting. Is that a normal phenomenon ? It feels like it’s not, but I’d rather ask.