Matt - Your right about just adding a "RouteOnAttribute" processor. I got
so caught up in trying to understand why a retry wasn't getting fired I
lost track of my original goal. I think I have a understanding of why the
"retry" was not getting fired now and that makes perfect sense. I will just
add
This might be intended behavior, it appears that only request
(incoming) flow files get routed to relationships like "retry", but
you have no incoming request flow file so there is technically nothing
to retry (the processor will "retry" the next time it runs). In your
case it sounds like you'd nee
Matt - No, I am not seeing this expected behavior. Nothing is being routed
to "retry" as expected. IF I set "Always Output Response" = true the
"Response" relationship is triggered and even in there you can see the
"invoke.http.statuscode=502" I have attached a screenshot to show you what
I mean. L
Jeremy,
The code implies that 502 responses (actually all 5xx responses) are
routed to "retry" [1]. Are you not seeing that?
Regards,
Matt
[1]
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/stand
