Replies: 1 comment 6 replies
-
Look at this example that limits send attempts: https://appsbyaaron.wordpress.com/2017/11/01/force-a-queued-message-to-error-if-the-number-of-send-attempts-exceeds-a-threshold/ You want to set the message state, not just throw. The throw causes the connector to think it just errored as if it were a timeout or processing issue. Setting the message state causes the message to drop out of the queue. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to work on a channel that performs a GET API call. This API call will often return an error response stating that there is no data in the time range given. When this response happens it isn't necessarily an "error" however. The destination has 3 retries, so I am trying to cut it off to not do additional retry attempts if that specific errors is returned on the first attempt. No matter what I have tried it is always doing the 3 retires before throwing my error.
I have been searching around these forums but cannot seem to get the results I am looking for. I saw something about having the destination response transformer inbound set to Raw and even that is not helping. Below is the code I have in my response transformer, am I missing something obvious here? Or is this even possible to do?
Beta Was this translation helpful? Give feedback.
All reactions