@MattWho  Thanks for your reply and let me know about the correct flow.   ... View more

@Ash1  Not clear from yoru query how files are getting into or out of your NiFi. Assuming you have already received a set fo FlowFiles for the day in to your NiFi dataflow, the best approach may be to notify if any fails to be written out /transferred at the end of your dataflow.  In this manor not only would you know that not all Files transferred, but would know exact what file failed to transfer. There are numerous processors that handle writing out FlowFile content (transfer) to another source or local file system.  Those processing components typically have relationships for handling various types of failures.  These relationships could be sent through a retry loop via the RetryFlowFile [1] processor back to the same transfer processor that failed.  You define in the RetryFlowFile processor how many times you want a FlowFile to traverse this loop.  After X number of loop it would get routed out of the loop to your PutEmail [2] processor where you could dynamically set the email content to include attributes from that FlowFile like filename, hostname of NiFi that failed to transfer it, etc... From the PutEmail processor you could send that FlowFile to somewhere else for holding until manual intervention was taken in response to that email. [`1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache.nifi.processors.standard.RetryFlowFile/index.html [2] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache.nifi.processors.standard.PutEmail/index.html   If you found any of the response given here assisted with your query, please take a moment to login and click "Accept" on each of those solutions. Thank you, Matt ... View more

@MattWho  Thank you so much for responding,    I want to rename the outgoing file as such "name_timestamp". want to name each file with the following standard "name"+"_"+"timestamp"   and the issue is solved after changing destination value from flowfile-content to flowfile-attribute initially it was pointing to flowfile-content and I dont see the custom extracted attributes in attribute section, but after changing to flowfile-attribute, I can see the extracted values in the attribute section   thank you very much ... View more

@midee  I just ran the test myself with your sample as a one line formatted json and it still worked. {"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations","id": "1155391","key": "DPGAUT-2","fields": {"customfield_10001": null,"customfield_10002": null,"customfield_10003": null,"customfield_10004": null,"customfield_10005": null,"customfield_10006": null,"resolution": null,"customfield_10101": "","customfield_10007": null,"customfield_10008": null,"customfield_10009": "This is required value","customfield_10010": null,"customfield_10011": null,"customfield_10012": null,"customfield_10013": null,}} Make sure your RouteOnContent processor dynamic property value does not have a line return in it. You'll notice it only shows "1" line above. If you see a "2" line then you have a line return in your Value field which would cause the issue you are seeing. Hope this helped, Matt ... View more

@ubetThe path to java.exe cannot have a blank space. ... View more

Hi Leopol, Hope I understand your needs. You may try using compressContent processor instead of UnpackContent, select uncompress mode and choose the compression format.     ... View more

@VidyaSargur We have not resolved the issue yet due to some priority shift. We're still seeing the same error. Will follow up on it soon. Ming ... View more