Grooming of scheduled jobs cascaded into other jobs with other settings?

PowerShell Universal
1

Hi

Upgraded to 4.4.1 this morning from 3.10.x.

I have a scheduled job, ScheduleAutomations, which in turn may start another long-running job, TransferFileInbound.

The output from TransferFileInbound is supposed to be kept for some time. I have a max-history of 1000 and grooming days 60 set. The output from ScheduleAutomations is not interesting and it has a max-history of 60 set.

The TransferFileInbound script can also be started manually a by a dashboard interface.

This has worked fine up until 4.x. It now seems like when the ScheduledAutomation jobs are groomed from the database, the invocations made by it of TransferFileInbound are groomed also and lost.

The manual invocations remain as expected.

Regards,
/Fredrik

Product: PowerShell Universal
Version: 4.4.1
2

Ok, have dug a bit further. I realize that 5.x presents child jobs as a tree, which at least somewhat might make this grooming behavior make sense. But that is not the case for 4.x where child jobs are just jobs in the interface. So in 4.x this grooming behavior makes no sense at all.

Also, I struggle to see the benefit of the new behavior with child-jobs as a tree in 5.x. As far as I’m concerned, this is an undocumented API change that upends an architecture I’ve been running successfully for three years through PSU 2, 3 and now partially 4.

I would like to be able to opt-out, or have an option to Invoke-PSUScript to have the script run detached from the script calling Invoke-PSUScript.