Occasionally, Iterable may not send a message to an intended recipient. When this
happens, it creates a send skip event for the user, including a reason field that
provides further details. Values for the reason field are described here:
| Reason | Applicable mediums | Explanation |
|---|---|---|
LocaleMismatch | General | User did not have a locale or its locale is not found in the project |
DataFeedError | General | Data feed returned a non-200 response code |
CatalogLookupError | General | Referenced catalog or field does not exist, and the #catalog Handlebars includes required=true
|
SnippetLookupError | General | Snippet does not exist and the Handlebars for the snippet includes required=true
|
RetriesExhaustedError | General | Iterable stopped attempting to send the message after several retries |
InvalidRecipientEmail | Iterable thought the email was valid but the ESP did not | |
InvalidReplyToEmail |
Reply To field contains an invalid email |
|
InvalidSender |
From field of the email is not authorized to send |
|
InvalidHostedUnsubscribeUrl | Hosted unsubscribe URL could not be made into a valid URL after rendering Handlebars | |
HandlebarsExecutionError | General | Handlebars expression in the template was invalid after applying merge params |
MessageServiceError | General | The message service returned a non-200 response code and it is not an error that Iterable specifically handles. |
EmptyContent | Email has no content at all (it doesn't even have <html> tags) |
|
DuplicateMarketingMessage | General | Iterable refused to send the marketing message because the same message was already sent to the target within the last 18 hours |
SuppressedByMessageService | SMS, Email | Target is on the message service provider's suppression list |
MisconfiguredMessageService | General | Message service provider or channel used to send was misconfigured. For example, the API key could be wrong. |
Comments
0 comments
Please sign in to leave a comment.