Error handling in the retry
processor
#125
Labels
needs investigation
It looks as though have all the information needed but investigation is required
processors
Any tasks or issues relating specifically to processors
Currently, the
retry
processor scrubs the error of the origin message. This can be confusing for users. Maybe it would be better to not scrub it at all and make sure it's set back to its original value if one of the child processors clears it? Or maybe it's best to scrub it and set it back if the child processors don't set some other error? Or append to it the error coming from child processors? Not sure what's the best tradeoff...Here's a sample config to experiment with:
The text was updated successfully, but these errors were encountered: