Hi Matt, thanks for your your answer. @MattWho wrote: From the look of your dataflows it appears you have two FlowFiles that you want to merge via the MergeContent processor. The order in which they are merged is important to you. This sounds like a use case better solved by using the "Defragment" merge strategy in the MergeContent processor rather then trying to use EnforceOrder processor. Sorry for not mentioning this. My workflow starts with a series of API calls to obtain data, that is converted into xml fragments. With the merge processor, I am trying to merge those xml fragments into one final XML file. Hence the order is important. The files can have different product_id attributes and I only want to merge files with the same product id. Therefore I am using the MergeProcessor with the Bin-Packing Algorithm. As far as I know (I just started using Nifi last month) it is not possible to control the order using this algorithm? @MattWho wrote: As far as your dataflow goes, I am having trouble reproducing the issue you described. I see my priority 2 file sitting in wait only until my matching priority 1 file arrives. The dataflow screenshot you shared also does not show a wait relationship being routed anywhere. Are you using the "retry" + "terminate" checkboxes on the wait relationship instead? If so, what are the retry settings configured? I hadn't configured the wait relationship yet. I was under the impression, the EnforceOrder processor would re-visit flowfiles in "wait" status once other priority 1 files have been processed. I routed the wait relationship to a RouteOnAttribute processor (is there another way?) which then routes back to EnforceOrder: The priority 2 file will now be processed, but the order, in which the files are merged, seems to be random. Sometimes its the correct order, sometimes its not.
... View more
