Juan,
Very good advice!
I've updated my loop to add a processor that will run each X seconds when a
retry is needed, that way it won't block the other request :
InvokeHttp --(failure)--> UpdateAttribute (increment a counter) -->
RouteAttribute (if counter lower than X will retry) --(if retriable
Good afternoon,
All processors have a scheduling tab or run every X time. I would set it at
your last invokeHttp.
If time is important look at the prioritizer settings too. So that you can
send through as example a more important flowFile.
On Dec 12, 2015 13:48, "Louis-Étienne Dorval" wrote:
>
Hi again,
The MergeContent works perfectly for my case! The flow I've described in
the previous email changed a bit, but still it's working as expected.
The only problem, now NiFi is much faster than the existing system running
in parallel (which is really good). I've done a "retry loop" describ
