PSU 1.6 beta 2(?) feedback - License not recognized / Schedules not firing

Testing PSU 1.6 Beta 2 (I think? PSD1 says beta3)

It seems the License is not recognized properly. Or, at the very least, Automation schedules aren’t running ( I assumed this was how it might handle that). Manual invocation is fine. There is no indication in the logs as to why they aren’t kicking off on schedule.
Though it does show the Next Execution date as 1901:


I’ve opened an issue for this and will follow up once I take a look. PSU1.6 - Schedules not firing · Issue #127 · ironmansoftware/issues · GitHub

1 Like

I’ve haven’t been able to reproduce this on the 1.6-beta3 build I’m testing. We’ll be releasing it later this week so we might need to just retest this.

1 Like

If I happen to figure it out I’ll keep you posted. When you release the new beta, I’ll try with that. Possibly worth noting I am testing this using the MSI installer.

1 Like

I have the same problem with version 2.0.3.
I created a new schedule by targeting my script.


Le schedule ne se programme pas.

Do you have any idea what I’m doing wrong?

thank you.


When setting up a continuous schedule, i get the date/time in red. However, it executes fine from what I can tell by looking at the log.

I am on 2.1.1.

for my part,
If I insert the code here it works.
The jobs are processed however I do not have the time of the next execution.

on the other hand, if I insert a script in the configuration file “script.ps1”.

I manage to execute on the other hand, I cannot program it.

I understood my problem, the script only must be in the ‘ProgramData \ UniversalAutomation \ Repository’ directory for this to work.

However, it changes the structure of my ‘repository’ folder.
I would have liked to put the scripts in a subdirectory.