From 6b72d95e4bd06cf298539e937aa5c13d4b954c37 Mon Sep 17 00:00:00 2001 From: Manohar Kumar P <89695803+Man07har@users.noreply.github.com> Date: Wed, 12 Oct 2022 02:45:36 +0530 Subject: [PATCH] Create operational error file (#2379) * created operational error file * Update content/roadmaps/107-nodejs/content/103-nodejs-error-handling/103-error-types/operational errors Co-authored-by: Kamran Ahmed --- .../103-error-types/operational errors | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 content/roadmaps/107-nodejs/content/103-nodejs-error-handling/103-error-types/operational errors diff --git a/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/103-error-types/operational errors b/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/103-error-types/operational errors new file mode 100644 index 000000000..a69784a34 --- /dev/null +++ b/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/103-error-types/operational errors @@ -0,0 +1,3 @@ +# Operational Errors + +Operational errors represent run-time problems experienced by correctly written programs. they are not really bugs but are problems attached to something else in our program. Examples of such errors can be a failure to connect to a database, failure to resolve hostname, request-timeout, invalid input from the user, and so on.