Notification Error Codes – mxHero Help Center

mxHERO records a notification each time something needs your attention: a storage account lost access, a rule failed, a directory sync had problems, and so on. This page lists every notification code you can see in Reports › Notifications and in notification digest emails, what it means, and what to do.

How notifications are organized

Each notification has a type, a level and a code.

Type	Covers
`MAIL`	Processing of a specific email (rules, storage, S/MIME, Store in AI)
`STORAGE`	Cloud storage accounts and mxHERO Shares content
`RULE`	Mailbox rule tasks and Drag and Drop folders
`PLATFORM`	Directory sync and dataset sync

Level	Meaning
`ERROR`	Something failed. Action is usually required.
`WARN`	Something partly failed or needs checking.
`INFO`	For your information. No action needed.

Notifications are kept for 30 days. To have them emailed to you as hourly, daily or weekly digests, see Notification Settings.

Note: In a digest email, every code that is not INFO is marked Action required.

Code reference

The Digest label is the text shown in notification digest emails. The Go to column is where the notification's link opens in the Admin Dashboard.

Email processing (MAIL)

Code	Level	Digest label	What happened	What to do	Go to
`storage_error`	ERROR	Storage processing error	Uploading or processing an email's files in cloud storage failed.	Open the email in Email Flow Logs to see the storage error. Check the storage account's access, quota and folder path. See Storage Upload Failures.	Settings › Integrations
`execution_failed`	ERROR	Rule execution failed	A rule action failed with a known error. The original email was delivered unchanged, unless the rule is set to bounce on error.	Open the email in Email Flow Logs and check the rule error. Correct the rule settings.	Rules › Rules List
`execution_unexpected_error`	ERROR	Unexpected rule execution error	An unexpected error occurred while running a rule.	Note the email's details from Email Flow Logs and contact support. See Getting Support.	Rules › Rules List
`smime_error`	ERROR	S/MIME processing failed	S/MIME processing (sign, encrypt, decrypt or validate) failed. The email was still delivered.	Check that the sender or recipient has a valid certificate in Settings › S/MIME Certificates. See S/MIME Validation Failures.	Settings › S/MIME Certificates
`store_in_ai_error`	ERROR	AI storage error	An email's content could not be stored in the Mail2Cloud Advanced AI index. Files in cloud storage are not affected. Not raised for Drag and Drop rules.	Check the rule's Store in AI scope in Settings › Integrations. If it repeats, contact support. See Store in AI.	Settings › Integrations

Cloud storage and mxHERO Shares (STORAGE)

Code	Level	Digest label	What happened	What to do	Go to
`storage_credential_no_access`	ERROR	Storage credentials lost access	A connected storage account's authorization stopped working (for example, the user changed their password or revoked access). The account shows as not synced. The account owner is also emailed a re-authentication link. Repeats at most once a day, for up to 7 days.	Re-authorize the account in Settings › Integrations › Accounts. See Re-authorizing Storage Accounts.	Settings › Integrations
`malware-detected`	ERROR	(code shown as is)	Malware was found in a file stored in mxHERO Shares. The file is blocked for everyone. The file owner is emailed.	Review the file in mxHERO Shares › Malware. Release it only if you're sure it's a false positive. See Malware Detection.	Reports › Notifications

Mailbox rules and Drag and Drop (RULE)

Code	Level	Digest label	What happened	What to do	Go to
`task_finished_with_error`	ERROR	Sync task finished with errors	A mailbox rule run finished, but some emails failed.	Open the rule's errors to see which emails failed and why. Fix the cause (often storage access) and reprocess.	Settings › Integrations
`task_finished_without_error`	INFO	Sync task finished successfully	A mailbox rule run finished without errors.	None.	Reports › Notifications
`connection_error_max_retry`	ERROR	Connection retries exhausted	mxHERO couldn't connect to a mailbox after repeated retries and stopped processing it.	Check the mailbox connection (authorization, password, IMAP settings) in Settings › Integrations › Accounts, then re-enable or re-run the rule.	Settings › Integrations
`STORAGE_USER_WITH_ERROR`	WARN	Storage user marked unhealthy	One storage account in a balanced pool kept failing and was set aside. Other accounts in the pool continue.	Re-authorize or fix that storage account. See Storage Load Balancing.	Settings › Integrations
`web_hook_deleted`	INFO	Webhook deleted	A folder watched by a Drag and Drop rule was deleted, or Box removed the folder's webhook. The Box account owner is emailed.	If unexpected, pick the folder again in the Drag and Drop rule. See Drag and Drop.	Reports › Notifications
`web_hook_moved`	INFO	Webhook path updated	A watched folder was renamed or moved. mxHERO updated the rule's folder path.	None.	Reports › Notifications
`web_hook_removed_by_move_conflict`	WARN	Webhook removed due to folder conflict	A watched folder was moved inside (or around) a folder watched by another rule. mxHERO stopped watching it.	Edit the Drag and Drop rules so no watched folder is inside another watched folder, then select the folder again.	Settings › Integrations

Directory and dataset sync (PLATFORM)

Code	Level	Digest label	What happened	What to do	Go to
`accounts_and_groups_source_sync_warning`	WARN	Account sync completed with warnings	A directory sync (Microsoft 365, Google Workspace) finished, but some accounts or groups weren't synced.	Open the notification for details. Check the directory connection and any filters.	Settings › Accounts and Groups
`accounts_and_groups_source_sync_error`	ERROR	Account sync failed	A directory sync failed. Accounts and groups weren't updated.	Check the directory app's authorization in Settings › Integrations › Applications, then run the sync again. See Accounts and Directory Overview.	Settings › Accounts and Groups
`dataset-sync-failure`	ERROR	(code shown as is)	A scheduled Dataset Sync failed, so the dataset is no longer being updated.	Open the notification: it names the dataset and storage account. If the account needs re-authorization, use Go to accounts. If the folder is missing or too large (over 100,000 items), fix the sync settings. See Datasets.	Reports › Notifications (links to the dataset and accounts)

Other

Code	Meaning
Other notification	A code the dashboard doesn't recognize. Open it for details, and contact support if it repeats.

Read a notification

Open Reports › Notifications.
Filter by date, level or type.
Click a notification to see its details. The details depend on the type:
- MAIL: the email (subject, sender, recipients, message ID)
- RULE: the rule and the watched folder
- STORAGE: the cloud storage and user, with a Go to storage accounts button, or the malware details
- PLATFORM: the directory sync or dataset sync details
Use the help icon next to the code for a short explanation and suggested action.