Level 8 error
This redirect may meet Wikipedia's criteria for speedy deletion as a very short article lacking sufficient context to identify the subject of the article. See CSD A1.
If this redirect does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this redirect may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this redirect has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by Unforgiven24 (contribs | logs) at 15:46, 21 August 2008 (UTC) (16 years ago) |
The level 8 error was first discovered in the early part of August 2008. It was originally intended to be part of an escalation system placed into use by IT departments worldwide. The original plan never came to fruition as the financial backers of the project preferred to use the 2 level system of "fixed or not". Currently a level 8 error refers to any problem that is easily identified and solved with minimal interaction. These include but are not limited to a computer mouse not working because it is not plugged in, or not being able to send an email to a specified address because that address is full as per the error message that is returned.[1] Level 8 errors are used in conjunction with modern business practices due to interoffice communication sometimes becoming unbearable.