System Response to Process Failures

Message Failure Due to Technical Issues

Messages that fail to deploy due to technical issues are placed in a retry queue. The system attempts to deliver the message periodically over a 72-hour period. If the system is unable to deliver the messages within the 72-hour window, the messages are marked as bounced.

Logs are available to identify delayed messages. An automated report could be created from these logs, and you can customize the report to include any available data.

Real-time campaigns have the same safeguards as batch campaigns. If a disruption of service occurs, real-time campaigns also include the ability to queue the API request . Real-time campaign API requests can also be received at a remote data center for processing.

Message Failure Due to Non-Technical Issues

An example of a non-technical issue is when an email address is not valid.

Messages that could not be delivered due to non-technical issues are logged. Automated extracts of these messages can be accomplished using the Marketing Cloud Engagement automation engine. Custom extracts can be created that contain any data we have available. No difference exists between real-time and batch campaigns.

Export Failures

An example of an export failure is when you require a feed of bounces, but an issue occurs that prevents the data feed from being exported, perhaps web service is unavailable.

Data exports can generate notifications when errors occur. Data exports support the ability to re-execute exports using the same parameters and returning the same data as a failed run. If the failure is due to an issue on the client's side, the system retries until the data can be delivered.