I have a powershell script that i am executing via System.Management.Automation.Powershell.Invoke. in the script i have Start-ThreadJob... | Wait-Job…
Running the script on the command line using pwsh.exe does exactly what i need it it do… the job starts and the Wait-Job causes the script to pause execution until the job is done before it moves on.
When I execute this same ps1 file using System.Management.Automation.Powershell.Invoke method, the Start-Thread Job command does not seem to be getting fired. The script just continues on and this is causing the rest of my script do not do anything else as it relies on the job I intend to start.

Since I know running the powershell command with pwsh on the command line works, I know my PowerShell logic is correct.
I also tested putting a Start-Sleep in my code and execute it through .Invoke and the script respected pause before returning back to my .net logic. I have tried Start-ThreadJob and Start-Job as well, neither seem to execute as expected. And I am coming up very short with any research.

I am excepting my .net client to allow the script to execute as designed. It should allow the PowerShell script to pause execution while a job is started and flagged as “Completed”. I can get the expected behavior if I run pswh as a process in dotnet and pass the arguments that way but I feel it should work though the api also.

The following code is an example of what seems to not be working:

$codeBlock = [scriptblock]::Create("kubectl wait --timeout=-1s --for=condition=Failed job/$batchStatus -n $namespace")
$stj = Start-ThreadJob -Name "$batchStatus-failed" -ScriptBlock $codeBlock 
"WaitFailed job state after apply: $($stj.Name)"
wait-Job -Id $stj | Out-Null

the “wait failed…” print out never shows the $stj.Name value, i assume that is because the $stj never gets fired

The PowerShell logic is in a file called Execute.ps1

this is my C# logic to execute Execute.ps1

System.Management.Automation.PowerShell ps = System.Management.Automation.PowerShell.Create();
ps.AddScript(File.ReadAllText(@"C:powershellexecute.ps1"));
var t = ps.Invoke();

I would think the ps.Invoke() would execute the function and wait for the powershell to be complete before it returns… the $codeBlock in the PowerShell should cause the script to process and wait on that job to complete. Again this works perfectly fine when I execute the PowerShell command on the pwsh command line, it is only when I execute it through System.Management.Automation.PowerShell I see this behavior