โ03-23-2020 12:06 PM
Error handling procedure is falling over internally and then trying to send error messages about itself, thus creating a loop, what can be done with the sender address or not to get this many alerts?
The error message we get is as follows:
{
โlogidโ: 1566
โPipelineRunTimeIdโ:
โโ
โPipelineRunTimeโ:
โ2020-03-23T18:05:23.903โ
โpayloadโ:
โhostname , pipeline name ,$= {error=Cannot deliver the message, reason=Message caused too many failures, resolution=Redirecting message that has caused too many failure to the error pipeline: {}, status_code=too-many-pipeline-failures, original={task_name=โฆโ
โStatusโ:
โorganization_ERROR_โ
โResponseMessageโ:
null
}
It is the error that the message could not be delivered ({error=Cannot deliver the message, reason=Message caused too many failures, resolution=Redirecting message that has caused too many failure to the error pipeline: )
After we experience a failure these messages were what the email sender was replaying nonstop.
Eventually the monitor email address gets flagged for excessive mails, and end up been blocked.
โ03-23-2020 12:17 PM
Increase your batch size to consolidate messages into fewer emails.
โ03-23-2020 12:50 PM
I do not think that is an option for us since we want the original payload to be sent to us in different batches. Besides the original payload received once we are getting this โerror=Cannot deliver the message, reason=Message caused too many failures, resolution=Redirecting message that has caused too many failure to the error pipeline:โฆโ