Developer's Analytics Bot Silently Reported Zero Stats for Two Months Due to Wrong Username in .env File

A developer discovered that his X (Twitter) analytics bot had been delivering completely useless weekly reports for over two months, always showing zero followers, likes, and impressions. The root cause was a single misconfigured line in the bot's .env file, where the target username pointed to a non-existent account instead of his own. Because the X API returns empty data rather than an error when queried with an invalid username, the script ran without throwing any exceptions and exited with a 200 OK status each time. The developer only investigated after noticing two months of consecutive all-zero Slack reports, eventually tracing the issue through the request payload during local debugging. The incident highlights how silent failures in automated side projects can go undetected when monitoring only checks for process completion rather than validating output data.