Notifications: Error Codes Reference
Table of Contents
This document provides a list of common error codes under Notifications, their meaning, and recommended actions.
The following information might be useful to:
- Understand what means a particular error or warning
- Identify the probable cause
- Apply corrective actions
Understanding Error Levels
ERROR → requires immediate action
WARNING → some functions might be affected
INFO → informative text
Module (origin) |
Code |
Type |
Level |
Description |
Suggested action |
|---|---|---|---|---|---|
storage |
storage_credential_no_access |
STORAGE |
ERROR |
The storage credentials/token (e.g., Box, OneDrive) lost access or became invalid. |
Reconnect/re-authorize storage credentials and validate provider permissions for the affected user. |
storage |
storage_error |
ERROR |
Storage mail processing failed or ended in relevant error/warn condition. |
Inspect execution details, validate storage access/quota/path, and retry affected flow. |
|
drag-and-drop |
web_hook_deleted |
RULE |
INFO |
A webhook linked to a rule/folder was deleted. |
Verify if deletion was expected; if not, recreate webhook mapping and review recent folder/rule changes. |
drag-and-drop |
web_hook_removed_by_move_conflict |
RULE |
WARN |
Folder move created a webhook conflict; webhook was removed to avoid inconsistency. |
Review conflict details, re-link folder/webhook, and validate rule path consistency. |
drag-and-drop |
web_hook_moved |
RULE |
INFO |
Webhook path/folder mapping was updated successfully. |
No urgent action; keep as audit signal and confirm rule still points to intended folder. |
emailsync |
task_finished_with_error |
RULE |
ERROR |
Sync task finished with one or more account/process failures. |
Open task execution details, identify failed accounts, retry targeted failures. |
emailsync |
task_finished_without_error |
RULE |
INFO |
Sync task finished successfully. |
No action required (monitoring/audit only). |
emailsync |
STORAGE_USER_WITH_ERROR |
RULE |
WARN |
A storage user was marked unhealthy due to repeated failures. |
Investigate last error cause, validate account/provider status, and re-enable user when stable. |
emailsync |
connection_error_max_retry |
RULE |
ERROR |
Maximum retries reached on connection failures. |
Check provider/API connectivity, credentials, throttling, and queue/backoff behavior before retrying. |
sources-sync |
accounts_and_groups_source_sync_warning |
PLATFORM |
WARN |
Source sync completed with warnings in accounts/groups/domains. |
Review warning counts/details and correct source data/config mismatches. |
sources-sync |
accounts_and_groups_source_sync_error |
PLATFORM |
ERROR |
Source synchronization failed with blocking error. |
Check source connector auth/API health, fix root cause, rerun sync safely. |
store-in-ai |
store_in_ai_error |
ERROR |
Content could not be stored in AI service. |
Validate AI service availability, payload constraints, and auth; retry failed operation. |
|
smime |
smime_error |
ERROR |
S/MIME processing failed (sign/encrypt/verify stage). |
Check certificates/keys/trust chain and message format, then retry processing. |
|
engine |
execution_failed |
ERROR |
Rule execution failed in a known/handled path. |
Review execution details for failed action step, fix rule/dependency issue, rerun if needed. |
|
engine |
execution_unexpected_error |
ERROR |
Rule execution failed due to unexpected runtime exception. |
Capture stack/context, escalate to owning dev team, and apply workaround/retry strategy. |