The dangerous urge to delete everything and rewrite the entire codebase

Every software engineer reaches a breaking point. You spent four hours trying to track down a silent bug in a legacy module, only to realize the architecture is a house of cards held together by deprecated libraries and prayer.
In that exact moment, a dangerous voice whispers in your ear: "Just delete the repository. We can rewrite this whole thing from scratch in a weekend."
It’s the ultimate developer fantasy. Starting fresh. Clean architecture. No technical debt. But as senior engineers know, a complete rewrite is almost always a trap that takes six months and introduces fifty new bugs.
Yet, sometimes... refactoring spaghetti code is just slow torture.
Where do you draw the line? When do you actually commit to a full rewrite, and when do you just swallow your pride and refactor the mess? Let's discuss in the comments.
P.S. If you are currently fighting the urge to delete your main branch, check out my profile bio for a badge of honor.