Halting on an error is often best, as is raising the error after catching it, unless you're certain it should be subdued or aware, expect the issue, and have limited risk.
Every dev project:
Hold up, couldn't this raise an exception? That's bad!
> In a revision to the Flight Crew Operations Manual, issued on January 15, 2024, Boeing confirmed that the door functioned as designed.
Problem solved for the current level in the hierarchy.
Literally turning a blind eye, but officially, so that’s okay!