I hit a weird Finder copy failure the other day.
This happened on macOS Sequoia. The copy failed partway through, and Finder suggested that I could resume it, but I was not very comfortable trusting that.
Once a copy operation has already failed, it becomes hard to tell whether the destination is still in a clean and trustworthy state. In this case, deleting the destination file or folder and starting the copy again from scratch felt like the safer option.
I would not call this a confirmed Finder bug based on a single case. It may also have involved file corruption, file permissions, or some other weird edge case, but it was odd enough that I wanted to write it down.