Get-PSUJobPipelineOutput returns no data for completed jobs (2026.3.x regression)

A fix for this issue has been implemented in version 2026.3.2
Implemented

Get-PSUJobPipelineOutput returns no data for completed jobs (2026.3.x regression)

avatar

Environment: PowerShell Universal 2026.3.1 (possibly already 2026.3.0)

Summary: After upgrading to 2026.3.x, `Get-PSUJobPipelineOutput` returns nothing for completed jobs, even though the pipeline output was produced correctly and is counted (but not shown) in the Admin Console.

Repro script:
$InformationPreference = 'Continue'

$obj1 = [PSCustomObject]@{ Fruit = 'Apple'; Count = 3 }
Write-Information "Object 1: $($obj1 | ConvertTo-Json -Compress)"
$obj1

$obj2 = [PSCustomObject]@{ Name = 'Widget'; Color = 'Blue'; 'Order-State' = 'Success' }
Write-Information "Object 2: $($obj2 | ConvertTo-Json -Compress)"
$obj2

$arr = 1..2 | ForEach-Object { [PSCustomObject]@{ Index = $_; Value = "Item$_" } }
Write-Information "Object 3 (array): $($arr | ConvertTo-Json -Compress)"
$arr

Steps: Run via Invoke-PSUScript (or admin console), wait for completion, then check the job's "Pipeline Output" tab and call Get-PSUJobPipelineOutput -JobId <id> (tested locally and remotely with -ComputerName/-UseDefaultCredentials).

Expected: 4 objects (array unrolls to 2) with their properties, retrievable via Get-PSUJobPipelineOutput and inspectable in the Admin Console (as in 2026.1.6).

Actual:
- Admin Console "Pipeline Output" tab lists 4 rows but only shows the type name Deserialized.System.Management.Automation.PSCustomObject, no property values.
- Get-PSUJobPipelineOutput -JobId <id> returns nothing, locally and remotely.
- The job Log tab (explicit `Write-Information` JSON) confirms the correct values were actually emitted, ruling out a scripting error.

Impact: Any dashboard app using Get-PSUJobPipelineOutput to show job results in a table silently displays empty data despite successful job execution.

All Comments (4)

avatar

Thanks for bringing this to our attention! I've opened a ticket for it, and we'll have a fix in a release soon (sometime after 2026.3.2).

avatar

This is highly impactful if you have scripts that rely on calling other scripts! I'm using `Invoke-PSUScript -Wait` in several scripts and those are all broken right now.

avatar

Thanks for letting us know how impactful this is. We've moved the fix for this into the next release (2026.3.2).

avatar

@pos-basic-infrastructure @realslacker 2026.3.2 is released, once you update, could you share your experience with us?

Thank you!

Best regards,

Marc-Antoine Dubois

A fix for this issue has been implemented in version 2026.3.2