How can my custom compiled cmdlet display the original error position from a thread job?

When using thread jobs, errors sent to the error stream by Receive-Job display the original error’s position message, showing where in the job the error occurred. However, if you write errors from your own compiled cmdlet (like Receive-JobFancy) using Cmdlet.WriteError(), the error position reflects the cmdlet’s location rather than the error’s originating location.

For example, consider this thread job code:

POWERSHELLCopied
$job =
    Start-ThreadJob {
        1/0 # error line
    }
$job | Wait-Job | Out-Null
$job | Receive-Job

which outputs:

TEXTCopied
RuntimeException:
Line |
   2 |          1/0 # error line
     |          ~~~
     | Attempted to divide by zero.

Now, using a custom cmdlet such as below:

CSHARPCopied
Add-Type @'
using System.Management.Automation;

[Cmdlet(VerbsCommunications.Receive,"JobFancy")]
public class ReceiveJobFancy : PSCmdlet {
    [Parameter(Mandatory = true,ValueFromPipeline = true)]
    public Job Job {get; set;}
    protected override void ProcessRecord() {
        foreach (var e in Job.Error) WriteError(e);
    }
}
'@ -PassThru   |
    % Assembly |
    Import-Module

$job =
    Start-ThreadJob {
        1/0 # error line
    }
$job | Wait-Job | Out-Null
$job | Receive-JobFancy

produces output with a position message corresponding to the line in the cmdlet rather than the original error:

TEXTCopied
Line |
  22 |  $job | Receive-JobFancy
     |         ~~~~~~~~~~~~~~~~/n     | Attempted to divide by zero.

This makes diagnosing errors more challenging. Although Get-Error shows the original error's position via $.Exception.ErrorRecord, it is less convenient for reviewing all job errors.

The question, then, is: How can I write an error from a job so that it displays the original error’s position message like Receive-Job does?

Below are suggested approaches by others, including extracting the inner error record or using reflection. The goal is to mimic Receive-Job by outputting the error record from the underlying exception, preserving the original invocation info.

Please share any improved methods or clarifications.