Hi - I have an issue where certain processors may hang due to misconfiguration. For example, an ExecuteStreamCommand with an incorrect path for the executable. In this scenario, the flowfile waits in the queue for the processor and cannot proceed. It generates an error message, both visually and in the log, but for the business process I'm working on we want to detect this condition within the flow and then route an error message to a queue. I was thinking about adding an expiration time for the flowfile, but I wasn't sure how to capture that notification. Any ideas? Is it possible to set up a processor that 'listens' for any expired flowfile and outputs its attributes?
Thanks, Dave
