I fixed the exact same error twice in one afternoon, in the exact same place, and it still wasn't fixed. The first fix worked -- I could tell because the error message changed. What I hadn't clocked yet was that it had changed into a second, nearly identical error from a completely different AP...
Source: [Dev.to](https://dev.to/just_a_side_project/debug-log-1-i-fixed-the-same-error-twice-in-one-afternoon-and-it-still-wasnt-fixed-3bo1)