Common Approved Email Errors
Removed 4/28. Doesn't seem to add doc value.
If validation of an email fails, the status of the email updates to Saved or Failed. Error messages for these sent emails enable admins and end users to better understand why an email failed validation. Error messages stamp on the Failure_Msg__v field on the Sent_Email__v object.
Below is a list of common Approved Email errors:
|
Scenario |
Error Message |
Status | MC Behavior | Resolution |
|---|---|---|---|---|
| Vault cannot authenticate integration user's credentials | Failed to authenticate against Vault. |
Saved__v |
Retry sending email on the next Scheduled job run |
Update the credentials for the Vault integration user in the Approved Email Administration page |
|
An Email Template/ Email Fragment in Vault is not approved |
At least one document included is not in approved state: Vault DNS:Doc Id | Failed__v | Do not retry sending email | Sync often to receive updated content on device |
|
An associated document of an Email Template and/or Email Fragment is not approved |
At least one associated document referenced is not in approved state: Vault DNS:Doc Id |
Saved__v |
Retry sending email on the next Scheduled job run |
Update the status of the associated document in question to steady state in Vault |
|
Vault CRM Integration user’s credentials are invalid |
n/a | Saved__v | The email is processed (and sent, if all validations pass) but the status of the sent email record is Saved__v. If the credentials are updated, the status will update the next time the scheduled job runs | Update the credentials for the Vault CRM integration user in the Approved Email Administration page |
|
Vault returns nothing, query timed out |
Vault query timed out when validating content. Email will be processed again when the Scheduler job runs next time. |
Saved__v |
*Retry procedure |
Issue should be resolved by retry logic |
| Vault returns empty results | Vault returned empty results when validating content. Email will be processed again when the Scheduler job runs next time. | Saved__v | *Retry procedure | Issue should be resolved by retry logic |
|
Vault returns Invalid session |
Invalid Vault session. Email will be processed again when the Scheduler job runs next time. |
Saved__v |
*Retry procedure |
Issue should be resolved by retry logic |
| Vault is down | Vault is down. Email will be processed again when the Scheduler job runs next time. | Saved__v | *Retry procedure | Issue should be resolved by retry logic |
|
Vault returns 500 |
Unknown Error from Vault. Email will be processed again when the Scheduler job runs next time. |
Saved__v |
*Retry procedure |
Issue should be resolved by retry logic |
| Vault is under maintenance | Vault is under maintenance. Email will be processed again when the Scheduler job runs next time. | Saved__v | *Retry procedure | Issue should be resolved by retry logic |
*Retry procedure: The email is processed two minutes after the initial attempt. This is for both ad-hoc and emails in Saved__v status. If the Retry Procedure is unable to process the email, the email will be processed the next time the scheduler runs.
