Preserve the cause, surface the right boundary message, and do not silently erase the operational clue.
The right failure path shortens the next debugging cycle instead of hiding it. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.
Additional Notes
What failure handling lens fits long-lived objects?