Hi All - I'm wondering if there is an approach to using the RetryFlowFile that doesn't get 'stuck' if there are lots of failures.  I'm using InvokeHTTP and if it fails, the failure goes to a RetryFlowFile process.  The retry from the RetryFlowFile goes back to InvokeHTTP.  If the InvokeHTTP process fails for a long time, the failure queue fills, the retry queue fills, and when InvokeHTTP is brought back up, it won't start since both queues are full.

Any ideas?
Thank you!

-Joe Obernberger

Reply via email to