Replies: 3 comments 1 reply
-
Is this because the queue is trying to reprocess the message? |
Beta Was this translation helpful? Give feedback.
-
Yes, the message is reprocessed from the queue, so that's why it errors again and you get another alert. I don't have a good idea for a workaround, but I'll leave this open in case other users want to comment. |
Beta Was this translation helpful? Give feedback.
-
I have a teammate working on a similar problem. We have an HTTP sender that will error because the customer is doing maintenance then succeed later after a few retries. We get an alert for each retry instead of just on the last error. He does not have any results yet but he is testing a responseTransformer that will:
I will do my best to report back if our solution works or not. |
Beta Was this translation helpful? Give feedback.
-
Description:
I have set up an alert for a Destination Connector whenever I get an ERROR.
I have one message stuck in a queue(intentionally) and I get a flood of alerts for the same message.
Expected behavior
I would like to get one alert per message-id per action(ERROR/SENT)
Actual behavior
A flood of alerts for the same message with the same ERROR
Screenshots
Environment (please complete the following information):
Beta Was this translation helpful? Give feedback.
All reactions