Operator Alert Faults Print

What this family covers, and why none of it is actionable

Eight named refusals, all raised by Log\OperatorAlertError, and every one of them is, in the shipping code's own words, "always a CODING fault, never a logging failure." This class exists solely to stop this module writing an alert row that looks like a real record but cannot actually be traced to a service, a server entry, a timestamp or a reason — because an alert an operator cannot act on is worse than no alert at all: it looks like evidence and is not.

None of these eight is triggered by anything a customer does, by any setting on a server entry or a product, or by any state IDrive e2 itself can be in. Each one fires only if the module's own internal code tried to build an operator alert while missing a piece of information that alert absolutely requires. If you ever see one of these eight codes, there is no field to fix and no setting to change: note the code and roughly when it happened, and report it as a defect.

The eight, grouped by what the alert was missing

• No subject to attribute it to: alert_owner_unidentified (no identifiable service named) and alert_server_unidentified (no server entry named, so no brand can be told which credential it concerns).
• No content to show: alert_name_empty (no name for the refusal, divergence or cron that happened) and alert_detail_empty (a divergence alert with no composed detail sentence).
• Bad or missing values: alert_count_negative (a count that cannot be less than nothing) and alert_time_empty (no timestamp, so the row could not say when).
• A reconciler report that would overstate its own coverage: alert_limits_empty (a report stating no checks it could not make, which would publish a clean bill of health it had not earned) and alert_limit_name_invalid (a stated-limit list holding something that is not a name, refused rather than silently coerced into looking like one).

Every one of these eight results in exactly nothing being written to the activity log — "NOTHING WAS LOGGED" is stated verbatim for each in the shipping message text. Nothing else on the service is affected either way.