I am working on some software where the notion of a "less severe" error has now come up as a case to handle, and for logging purposes I want a term to use to represent these. The first to come to mind was "Soft Failure", as I am using "Failure" for the regular more-serious issues. If I do that, though, then it seems like I should rename the original to "Hard Error" by contrast. I'd really rather stick with single-word names, or at least have it be unrelated to the existing Success/Failure dichotomy.
I know this question might be a bit pedantic, but please forgive that as I'm a nut for properly naming things in a concise and descriptive way in my software (which any of you who program know is a good thing for anyone else who works with it).
Currently I'm leaning toward using "Fault", as it almost fits, but a better suggestion would be welcomed.
Edit: Since others seem to have a bit of the wrong idea of what I mean, let me clarify. The term would not be used to refer to a completely unexpected failure - that's what "Failure" is for in the system. This is for expected but rare events that aren't good but aren't a problem in the software. For example, you connect to a database and try to grab a value, but the connection times out due to latency. Another example could be that upon trying to get a value it is missing from the database entirely. Again, this isn't "broken", it's just a missing piece of data, but everything is operating properly. That makes things like "glitch" and "bug" feel ill-suited.