Read-host in the Portal resets to the form
First, I like how the portal visually handles the Read-Host prompt now.
However, after entering the data, it rests to the form and hides the ongoing job output.
Removing the Read-Host from the same script fixed the issue.
The job and its output are still visible in the history.
If the Script contains a Second Read-Host the feedback can not be supplied over the Portal, also not over the history tab.
Version: 2026.3.3
All Comments (2)
Hello Dy,
Thank you for the report, and I am glad the new prompt looks good to you.
I reproduced both parts in our lab on PowerShell Universal 2026.3.3 in Docker. After the answer to the first Read-Host is submitted, the Portal page goes back to the script form and the job's output disappears, while the job keeps running. When the job reaches the second Read-Host, the Portal page does not show it, and the job's page under History offers no way to answer it either.
This is a defect in how the Portal page follows the job after an answer, and I have written up our steps to reproduce it for our QA team.
Until it is fixed, two things worked in the lab. You found that removing the Read-Host fixes it, and declaring those values as script parameters instead lets the Portal form ask for them before the run, so the page then follows the job to the end. That works when the values are known before the script starts, not for an answer that depends on something the script shows first. A prompt that is already waiting can also be answered from the admin console, on that job's page under Jobs, with the Respond to Feedback button. That needs someone who can open the admin console, so it does not help a user who only has the Portal.
Best regards,
Michel
Michel Audi
No pressure on that one.
Some of my clients only have very low-level PowerShell scripts, and I just want to show them that they can plug and play their existing scripts to make adoption easier.