Benefits / Use Cases of Queue Messages ->On Failure vs Always #5739
Unanswered
JeffBenedict
asked this question in
Frequently Asked Questions
Replies: 1 comment
-
Always is truly asynchronous. It will queue every single message. Queue On Failure is only asynchronous when there is an error. So successful messages will not queue and send synchronously. Failed messages will queue. IMO "Always" is a better default choice because the behavior is consistent for every message. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In MC 3.x +, under Destination Settings/Queue Messages; I read and understand the definition of On Failure vs Always. We have ours primary set to On Failure. Can someone explain use case as to when / why we'd want to use "always" ? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions