how to handle errors when using branch processor
#3750
Replies: 1 comment
-
|
nevermind (the |
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
Uh oh!
There was an error while loading. Please reload this page.
-
I currently have this:
The branch request mapping results in something like this:
The intention of this entire thing is:
branch(i need that later)The problem: the most likely step in this entire pipeline which can fail is "transfer file" (due to network issues). When that happens, I want to reject the message and let NATS send it again and again (I might need to put a rate limit in there too, to ease processing, when the network recovers).
Anyway, I was playing around with things like
reject_errored, only wondering why it doesn't do anything. So I modified the pipeline a little (like shown above) to test a theory. If the message would be flagged as "errored" i would not see any new messages in my output NATS subject. But I do.So, for me it looks like, as if errors in a branch, does not flag the original branch (payload) as "errored". Is that really so? What am I missing?
Beta Was this translation helpful? Give feedback.
All reactions