Signed in as Russ

The mistake

A nightly automation script runs under a named user's personal login instead of a dedicated service account, so every job it kicks off — including failed ones — gets logged and audited as actions taken by that person. When the script errors out and corrupts data or breaks a deploy, the failure trail says the human signed in and did it, not that a cron job under their stored credentials did. Nobody rotated the script to its own service identity, so the attribution has been silently wrong for as long as the script has been failing.