Did you find a solution?  It makes sense to put a protected password field on a single processor (or controller service). The password won't be passed as an attribute along the flow.   It does not make sense to put a (protected) password into a flow attribute, because the password will be exposed.   So just make sure that your nifi/-registry is secure. Make sure that the FTP user has limit capabilities. ... View more

@David Miller Hi David, You are right with being carefull sending to many emails and that there will be situations where monitoring/errorhandling needs to be adjusted individual. But I want a standard process for the majority of always repeated occuring errors. You know, not reinventing the wheel every time again. And if one day my processes are designed further there won't be emails sent just logging everything and give the support some kind of graphical interface (dashboard) - that's the plan. ... View more

So along the flow I have an attribute, which is called asin (aka product ID). The flow should fail when an ID already exists in a local csv file. With your help I changed my code to #!/usr/bin/python import os import java.io flowFile = session.get() productFound = False if (flowFile != None): if os.path.exists('/home/nifi/products.csv'): asin = flowFile.getAttribute('asin') with open('/home/nifi/products.csv') as csv: if asin in csv.read(): productFound = True if productFound: session.transfer(flowFile, REL_FAILURE) else: session.transfer(flowFile, REL_SUCCESS) I falsely assumed that I could call REL_FAILURE/SUCCESS multiple times. ... View more