Sometimes this kind of error handling is the cause of program slowdowns. So the API fails, but the program retries anyway, and so fails again endlessly. The user doesn't see anything from this happening, only that "the app is slow". Windows is plagued by this kind of behaviour. Its both what the article suggests can cause this, but throwing and ignoring exceptions can have this effect too.
The goal, IMO, would be to force the app not to try (or not to try once it failed) something that is bound to fail.
The goal, IMO, would be to force the app not to try (or not to try once it failed) something that is bound to fail.