AI-inserted em dash in PowerShell script silently killed automation stack for five days
A Windows automation stack running Claude Code CLI sessions went completely offline from August 26 to August 30, 2026, due to a single Unicode character in a shared PowerShell script. During a routine self-edit, an AI session added an idempotency guard to the central launcher file, including a comment that used a typographic em dash instead of a plain hyphen. Because the file was saved without a UTF-8 byte-order mark, PowerShell misread the encoding and failed to parse the script, silently crashing every scheduled task that depended on it before any log file could be created. No errors were recorded anywhere, making the outage invisible until four days of missing activity finally formed a recognizable pattern. The fix, deployed on August 31, involved correcting the file encoding, and forensic timestamps confirmed the exact AI session and character responsible for the failure.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in