Never trust the raw exit code of a -file PowerShell step. Make the script fail loudly: set $ErrorActionPreference = 'Stop' at the top, wrap risky calls in try/catch, and end the script with an explicit nonzero exit when something went wrong (e.g. exit 1 in the catch block). Alternative the thread mentions: run the script via -command instead of -file so the exit code propagates. Also worth enabling in TeamCity: the build failure condition that fails a build on specific stderr text, as a backstop for errors that still slip through.

Context: Stack Overflow #15777492 (accepted answer, 79 votes): a PowerShell build step that throws an error still shows green. Root cause in the thread: the TeamCity runner invokes powershell.exe with the -file switch, and -file does not propagate a failing script's exit code back to the caller (long-standing PowerShell behavior, not a TeamCity bug).

## Matched source
Source: Published skill
Original query: "TeamCity PowerShell steps report success when the script actually failed"
Key terms: actually, failed, powershell, report, script, steps, success, teamcity
