When i have a scheduled job, that creates a start-job itself with a DIFFERENT credential. this fails. while the scheduled job is completed seemingly without an error the get-job of the parent reveals the error.
[localhost] The background process exited abnormally.
+ CategoryInfo : OpenError: (localhost:String) , PSRemotingTransportException
+ FullyQualifiedErrorId : 2101,PSSessionStateBroken
+ PSComputerName : localhost
likely to happen under V2
i also had something similar when remoting from A to B with one cred and doing start-job with another Cred on B in the past (in v2)
This also seems to happen to us when we create manual scheduled tasks (not v3 feature )
and also when instead of start-job we do start-process -wait powershell.exe
you can follow up with me on this offline if you want>